XMemo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XMEMO_KEY | Yes | Your XMemo API token. Required for authentication. | |
| XMEMO_URL | No | The base URL of the XMemo service. Defaults to https://xmemo.dev. | https://xmemo.dev |
| MEMORY_OS_URL | No | Compatibility alias for XMEMO_URL. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mcp_identityA | Check XMemo connection status and the connected account/agent. Call this when the user asks whether XMemo is connected. |
| rememberA | 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_expenseA | 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_stateA | 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_contextA | 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_contextB | |
| list_ledger_transactionsA | 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_summaryA | 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. |
| record_eventA | Record a significant session event, milestone, decision, or handoff note useful for reconstructing recent work. Not for durable facts/preferences (use remember). |
| get_timelineA | Show recent events. Call this when the user asks what happened recently or when resuming work that may depend on recent events. |
| create_memory_todoA | 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_todosA | 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_todoA | 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. |
| recallA | 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_memoryA | 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. |
| forgetA | 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_statsA | 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_memoryA | Restore a previously deleted memory. Call this only when the user explicitly asks to restore or undo a deletion. |
| explain_memoryA | 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_versionsA | Show version history for a memory. Call this when the user asks for previous content or changes over time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| remember | Save a memory to XMemo for future recall across sessions. |
| recall | Recall relevant memories from XMemo before answering a question. |
| project-context | Build a context pack from XMemo for the current project or task. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yonro/memory-os-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server