XMemo
XMemo is the cloud memory layer for AI agents: a hosted, user-owned remote MCP memory system that gives Copilot, Claude, ChatGPT, Cursor, Gemini, IDEs, CLIs…
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Get Mcp Identity: Check XMemo connection status and the connected account/agent. Call this when the user asks whether XMemo is connected.
- Remember: Save a memory so it can be recalled in future conversations. Call this whenever the user states a durable fact, preference, instruction, identity or profile detail, project detail, or recurr
- Add Expense: Record one expense in the XMemo Ledger. Call this whenever the user states a concrete expense, purchase, income, or refund — for example, 'I spent 25 on lunch' or 'log this expense' — not
What data it sees
Do you need an account
No: the server works without sign-in
XMemo is the cloud memory layer for AI agents: a hosted, user-owned remote MCP memory system that gives Copilot, Claude, ChatGPT, Cursor, Gemini, IDEs, CLIs, and other agents the same durable context. Store preferences, project knowledge, decisions, reminders, and code logic once, then recall, search, update, and govern that memory across tools instead of rebuilding context in every conversation.
Server tool list (25)
Raw names from tools/list. Only developers need these.
| get_mcp_identity | Check XMemo connection status and the connected account/agent. Call this when the user asks whether XMemo is connected. |
| remember | Save a memory so it can be recalled in future conversations. Call this whenever the user states a durable fact, preference, instruction, identity or profile detail, project detail, or recurring workflow likely useful later — you do not need an explicit 'remember this'. Skip transient chit-chat. For spending, income, refunds, or bookkeeping requests, use add_expense. |
| add_expense | Record one expense in the XMemo Ledger. Call this whenever the user states a concrete expense, purchase, income, or refund — for example, 'I spent 25 on lunch' or 'log this expense' — not only on an explicit 'record this'. Capture date, amount, currency, item, and merchant/category when present. |
| update_state | Save the current working state during long-running work — active task, next action, or blocker — so future turns/sessions can resume. For durable user facts use remember. |
| recall_context | Build a context pack from XMemo memories. Call this before answering or planning when the task could benefit from multiple saved memories — preferences, prior conversations, projects, decisions, TODOs, or long-running work. |
| get_project_context | Assemble a structured project context pack for the given project. Args: project_id: Project identifier (the project scope). bucket: Bucket filter (default "%" for all buckets). team_id: Optional team focus. max_items: Maximum context items. max_tokens: Maximum rendered tokens. include_durable_context: Whether to include long-lived durable context. durable_query: Optional query to focus durable context. recent_hours: Hours of recent activity to include. output_json: Return the full JSON pack instead of a text summary. |
| list_ledger_transactions | Show XMemo Ledger records. Call this when the user asks about past expenses, purchases, or spending history, or before answering a finance question that depends on recorded transactions. For item searches use query and leave currency blank unless a currency was requested. |
| get_monthly_ledger_summary | Summarize Ledger totals by month and currency. Call this when the user asks for monthly spending, income, refunds, net balance, budget review, or spending trends. |
| query_audit | Advanced audit query. source='events' queries action/time/target audit events (for normal users prefer memory_activity); source='consolidation' inspects consolidation/lifecycle/reflection audit records (admin). Consolidates the legacy query_audit_events/query_consolidation_audit tools. |
| record_event | Record a significant session event, milestone, decision, or handoff note useful for reconstructing recent work. Not for durable facts/preferences (use remember). |
| get_timeline | Show recent events. Call this when the user asks what happened recently or when resuming work that may depend on recent events. |
| create_memory_todo | Create a TODO/action item in XMemo with an optional due time. Call this when the user asks to save a task, follow-up, action item, or reminder-style item to revisit later. |
| list_memory_todos | List open or completed TODO/action items. Call this when the user asks what tasks, follow-ups, or saved action items are pending or done. |
| complete_memory_todo | Mark a TODO/action item completed. Call this when the user says a saved task is done, resolved, or no longer needed; use the exact reference from list_memory_todos. |
| update_project_todo | Transition a project TODO's status. action must be one of: accept, assign, block, unblock, complete, cancel. assignee_agent_id is required for action='assign'; reason is required for action='block' (optional for cancel); note is optional for action='complete'. Consolidates the legacy accept/assign/block/unblock/complete/cancel_project_todo tools. |
| update_project_decision | Transition a project decision. action must be one of: resolve, supersede, reopen. resolution is required for action='resolve'. new_context (and optionally options_json/impact_level/resolution_note) is required for action='supersede'. Consolidates the legacy resolve/supersede/reopen_project_decision tools. |
| recall | Recall the few most relevant saved memories before answering, when prior preferences, known facts, past decisions, or project context may directly affect the response. Use recall_context when many memories are needed. |
| update_memory | Update the content, location, or type of an existing memory. Call this only when the user explicitly asks to correct, revise, move, or reclassify a specific saved memory. |
| forget | Permanently delete one memory by natural target ('latest', 'current', or an exact ID). Call this only when the user explicitly asks to forget/delete a specific memory; search or check activity first if the target is ambiguous. |
| memory_stats | Show aggregate statistics for XMemo memories — counts by type, source, location, and optional time range. Call this when the user asks for counts, breakdowns, or distributions. |
| restore_memory | Restore a previously deleted memory. Call this only when the user explicitly asks to restore or undo a deletion. |
| explain_memory | Explain why a memory exists or matched a query. Call this when the user asks why something was saved or why it was retrieved. |
| list_memory_versions | Show version history for a memory. Call this when the user asks for previous content or changes over time. |
| list_memory_conflicts | List conflicting/inconsistent memories. Call this when the user/admin asks to review unresolved conflicts. |
| resolve_memory_conflict | Resolve a listed memory conflict. Call this only when the user/admin explicitly chooses a resolution strategy. |