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. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_mcp_identityA | Checks XMemo connection status and the currently connected account/agent when the user asks whether XMemo is connected. |
| rememberA | Save durable information for future recall; skip transient chat. Existing Projects paths attach automatically. The create_project compatibility input may create a missing project only when explicitly enabled. Use add_expense for financial records and create_memory_todo for actionable work. |
| update_stateA | Create or replace one scoped working-state record for resuming a task, next action, or blocker. Requires memory:write; it versions that state slot and refreshes its expiry without deleting other memories. Use remember for durable facts or record_event for history. Provide content or a structured state field; ttl_seconds=0 means no expiry. |
| recall_contextA | Build a read-only, bounded context pack from multiple relevant memories. Use it when an answer needs several memory items or scoped/path-filtered context; use recall for a quick best-effort lookup or get_project_context for a whole-project snapshot. max_items/max_tokens bound output: memories that do not fit are omitted and reported, so raise max_tokens or use recall when you need the records themselves. |
| get_project_contextA | Read one authorized project's bounded context pack: state, TODOs, decisions, timeline, recent memories, and optional durable recall. Requires memory:read; it does not mutate project memories, and access is audit-logged. Use an exact project_id for a whole-project snapshot; otherwise use recall_context. max_items/max_tokens bound the whole pack; recent_hours affects only timeline; durable_query requires include_durable_context. |
| query_auditA | 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_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 | Read authorized timeline events newest first. Requires memory:read and makes no memory changes. Use it for recent history or session resumption; use recall_context for semantic multi-memory context. limit is clamped to 1-500; session_id and event_type are exact filters. |
| create_memory_todoA | Creates a TODO/action item in XMemo with an optional due time when the user asks to save a task, follow-up, action item, or reminder-style item to revisit at a later time. |
| list_memory_todosA | Lists open or completed TODO/action items as a concise text answer when the user asks how many tasks, follow-ups, or saved action items are currently pending or completed; do not use it to open, browse, filter, or manage the visual TODO workspace. |
| complete_memory_todoA | Marks a TODO/action item completed when the user says a saved task is done, resolved, or no longer needed; its exact memory reference is shown by list_memory_todos. |
| update_project_todoA | 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_decisionA | 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. |
| create_restart_snapshotA | Save active state, recent events, TODOs, and pending decisions for restart. Call this before handoff or when context may be lost. |
| restore_restart_snapshotA | Resume previous work from a saved snapshot. Call this when the user asks to resume/restart or after context loss. |
| recallA | Recall a few relevance-ranked memories before answering, with path/type controls and optional working-memory preference. Use it for a quick best-effort lookup; use recall_context when the answer needs a bounded multi-memory context pack. |
| update_memoryA | Updates the content, location, or type of a specific saved memory when the user asks to correct, revise, move, or reclassify it. An exact reference identifies the record. |
| forgetA | Delete one memory, TODO, or Ledger transaction by current/latest, an exact memory reference, an exact TODO ID from list_memory_todos, or an exact transaction ID from list_ledger_transactions. The default is a recoverable soft delete that restore_memory can undo; mode='hard' is permanent and unrecoverable and may be used only after the user explicitly confirms permanent deletion. Resolve ambiguous targets before deleting. |
| memory_statsA | Shows aggregate statistics for all saved XMemo memories — counts by type, source, location, and optional time range 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 | Explains why a memory exists or matched a query whenever the user asks why something was saved there or why it was retrieved. |
| read_memoryA | Read one exact authorized XMemo memory in character windows. Use a memory ID returned by recall or search, then continue long content with next_offset. Embeddings are never returned. |
| list_memory_versionsA | Show version history for a memory. Call this when the user asks for previous content or changes over time. |
| list_memory_conflictsA | List conflicting/inconsistent memories. Call this when the user/admin asks to review unresolved conflicts. |
| resolve_memory_conflictA | Resolve a listed memory conflict. Call this only when the user/admin explicitly chooses a resolution strategy. |
| propose_writeA | Propose a write operation (memory, todo, profile etc.) when direct modifications are denied due to tier-gating. |
| propose_todo_mutationA | Propose a todo mutation under the proposals bucket at path 'todos/{action}'. |
| propose_profile_mutationB | Propose a profile mutation under the proposals bucket at path 'profile.{field}'. |
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 |
|---|---|
| XMemo MCP quick start | Installation, authentication, and connection guidance for XMemo MCP. |
| XMemo security and privacy | Credential handling, privacy boundaries, and destructive-action guidance. |
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