ChatGPT Plugin

XMemo

Memory across conversations

Brand: XMemo

Category: Productivity
Primary Subcategory: Personal AI Memory & Second Brain

Integration details

Description

XMemo gives ChatGPT a private, persistent workspace that carries useful context across conversations. It can save, search, recall, read full memory text, explain, update, and organize preferences, decisions, project context, reference notes, TODOs, and personal Ledger records. Interactive TODO Board, Ledger, and Project Workspace views turn remembered context into structured work without leaving ChatGPT. OAuth and server-enforced scopes restrict every operation to the signed-in user's authorized data, while recoverable deletion, restoration, and explicit confirmation for permanent deletion keep users in control.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Personal AI Memory & Second Brain
Secondary Subcategories: None listed
Brand: XMemo
Access: Account required
First tracked: 2026-06-17
Tool count: 21
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Personal AI Memory & Second Brain

View Category

Listed in alphabetical order

Primary Subcategory

2MindComing soonGet notified

AI PassportComing soonGet notified

AI Whisper Voice Note TakerComing soonGet notified

AI WisebaseComing soonGet notified

AiAkiv MemoryComing soonGet notified

XMemoComing soonGet notified

Tools

21 tools agents can invoke

Use this when the user asks how often an exact word or phrase appears across visible XMemo memories, optionally grouped by day, month, source, location, or type. Use search_memory when the goal is retrieval rather than counting text.
analyze_memory_text
Use this when an answer, task restart, or handoff needs several relevant memories in one bounded context pack. max_items and max_tokens limit the read-only result; use recall for a quick best-effort lookup or search_memory for strict targeted matching.
recall_context
Use this when the user asks whether XMemo is connected, which account is connected, or which memory scopes were granted. It changes no state and returns no internal tenant, token, or diagnostic identifiers.
get_mcp_identity
Use this when the user asks why one exact memory was saved or why it matched a query after recall or search_memory. It reads retrieval and version context without changing the record.
explain_memory
Use this when the user explicitly asks to delete one exact memory, TODO, or Ledger transaction. Select a TODO by exact TODO ID. It defaults to recoverable soft deletion; use mode='hard' only after explicit confirmation of permanent deletion. Resolve ambiguous targets first.
forget
Use this when managing Ledger records. For 'I paid 199 CNY for a membership', use ledger(action='add_expense'). For current-month totals use action='summary', months=1, and owner_timezone.
ledger
Use this when the user wants to create, update, complete, or list authorized XMemo TODOs, or explicitly requests a recoverable bulk soft-delete. For action='list', provide the user's real IANA owner_timezone (for example, Asia/Tokyo) unless a saved owner profile supplies it. list rejects mutation-only fields and item_status must be open, in_progress, completed, or all. create requires client_mutation_id; update requires todo_id, expected_version, and client_mutation_id. delete_all requires explicit confirmation and confirm_delete_all=true. Use open_todo_board for visual browsing and forget(target=<TODO ID>) to delete one exact item.
todo
Use this when the user explicitly wants to create or change an authorized project or one of its memories, decisions, documents, conversations, or settings. Project/create requires name and no project_id; other actions require an exact project_id. Edits and unlinks require the matching reference and expected_version; memory edits use memory_ref (never memory_id). Use open_project_workspace or get_project_summary for reads.
project
Use this when the user wants to open the visual Ledger or external-service Renewal reminders. view=subscriptions is a compatibility value, not an XMemo plan. Requires a real IANA owner_timezone. Read-only; changes no data. Use ledger for totals, rows, or recording; widget edits run through ledger; deletion stays in Chat with confirmation.
open_ledger
Use this when the user wants to open or browse projects visually. With no project or an ambiguous name, it opens Project Workspaces Home; one unique authorized project opens its eight-tab workspace. Use get_project_summary for a concise text status, open_todo_board for standalone TODOs, and open_ledger for Ledger.
open_project_workspace
Use this when the user wants to open, browse, or filter TODOs visually. It requires the user's real IANA owner_timezone and only reads data; use todo(action='list') for text results, todo(create|update|complete) for writes, or forget(target=<TODO ID>) after explicit user intent to delete one exact item.
open_todo_board
Use this when the user wants a brief status, blockers, progress, or next-actions answer for one exact authorized project. It returns concise text only; use open_project_workspace to browse or manage the project. If the project cannot be resolved exactly, do not guess—direct the user to Project Workspaces Home.
get_project_summary
Use this when the user wants more content from one exact memory already identified by recall or search_memory. It returns one bounded character page with pagination metadata and never returns raw embeddings; use recall_context when several memories are needed together.
read_memory
Use this when the user refers to something they saved and a quick best-effort lookup is enough. It returns a few relevance-ranked memories; use search_memory for strict targeted matching or recall_context for a bounded multi-memory context pack.
recall
Use this when the user explicitly wants to record one significant milestone, decision, or handoff in the XMemo timeline so recent work can be reconstructed. Use remember for durable facts or preferences and update_state for the current resumable checkpoint.
record_event
Use this when the user explicitly asks to remember something or clearly states durable information they want carried forward. Skip transient chat and sensitive secrets. Use Ledger, not generic memory, for financial records. Existing project paths attach, but a missing project must first be created with project(entity='project', action='create').
remember
Use this when the user explicitly asks to restore or undo the recoverable soft deletion of one exact memory. Hard-deleted or redacted records cannot be restored.
restore_memory
Use this when the user wants a targeted XMemo lookup where weak matches must not be returned as answers. It searches with strong-match semantics; use recall for a quick best-effort lookup, recall_context for several memories, or forget for deletion.
search_memory
Use this when the user asks for one XMemo workspace view. For a broad snapshot or what XMemo remembers without explicitly asking for counts, grouping, or recent changes, call only the default overview with no optional arguments. Use section='stats' only for an explicit count or breakdown, and section='activity' only for explicitly requested recent changes. Never call multiple sections for one broad overview request.
memory_overview
Use this when the user asks to correct, revise, move, or reclassify one exact saved memory already identified by recall or search_memory. It preserves revision history.
update_memory
Use this when the user wants to save or refresh one resumable checkpoint with the current task, next action, or blocker. It versions the same scoped state slot; use remember for durable facts or record_event for history. ttl_seconds=0 means no expiry.
update_state

FAQs

XMemo ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve XMemo's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are XMemo alternatives on ChatGPT?

As of 2026-11-02, XMemo competes with 2Mind, AI Passport, AI Whisper Voice Note Taker, AI Wisebase, AiAkiv Memory, AideMemo, Areta, AristAI Thinker and 114 more in ChatGPT Personal AI Memory & Second Brain, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.