Celiums Memory vs Memory Os Cli
A side-by-side look at the Celiums Memory and Memory Os Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Celiums Memory for knowledge & memory work as a local process; choose Memory Os Cli for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Celiums Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SQLITE_PATH, DATABASE_URL, QDRANT_URL, VALKEY_URL, CELIUMS_API_KEY, PORT, CELIUMS_LLM_API_KEY, CELIUMS_LLM_BASE_URL.
Choose Memory Os Cli when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
get_mcp_identity, remember, recall.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 56/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | Free | Free |
| Required env vars | SQLITE_PATHDATABASE_URLQDRANT_URLVALKEY_URLCELIUMS_API_KEYPORTCELIUMS_LLM_API_KEYCELIUMS_LLM_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 23 | 12 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 20 |
| Full listing | View Celiums Memory | View Memory Os Cli |
Tools & capabilities
Celiums Memory tools
No tool names declared yet. Check the project README from the listing page.
Memory Os Cli tools 20
get_mcp_identityCheck XMemo connection status and the connected account/agent.rememberSave a memory so it can be recalled in future conversations.recallRecall the most relevant saved memories before answering.recall_contextRead a multi-memory context pack. Requires memory:read and does not change content. Use when many memories need explicit budgets; use recall for lightweight answer or get_project_context for project snapshot. max_items/max_tokens bound rendered output.memory_statsShow aggregate statistics for XMemo memories.update_memoryUpdate the content or metadata of an existing memory.explain_memoryExplain why a memory exists or matched a query.restore_memoryRestore a previously deleted memory.add_expenseCreate one XMemo Ledger transaction and backing memory. Requires memory:write; it records a new transaction or reuses a semantic duplicate, and never deletes Ledger records. Use it for a purchase, income, refund, or transfer; use list_ledger_transactions or get_monthly_ledger_summary for reads. amount must be positive; transaction_type defaults to expense; blank transaction_date uses today's UTC date.list_ledger_transactionsShow XMemo Ledger records.get_monthly_ledger_summarySummarize Ledger totals by month and currency.forgetPermanently delete a memory by target.- +8 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Celiums Memory
{
"mcpServers": {
"celiums-celiums-memory": {
"command": "npx",
"args": [
"-y",
"@celiums/memory"
],
"env": {
"SQLITE_PATH": "YOUR_SQLITE_PATH_HERE",
"DATABASE_URL": "YOUR_DATABASE_URL_HERE",
"QDRANT_URL": "YOUR_QDRANT_URL_HERE",
"VALKEY_URL": "YOUR_VALKEY_URL_HERE",
"CELIUMS_API_KEY": "YOUR_CELIUMS_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE",
"CELIUMS_LLM_API_KEY": "YOUR_CELIUMS_LLM_API_KEY_HERE",
"CELIUMS_LLM_BASE_URL": "YOUR_CELIUMS_LLM_BASE_URL_HERE"
}
}
}
}
Memory Os Cli
{
"mcpServers": {
"yonro-memory-os-cli": {
"command": "npx",
"args": [
"-y",
"--package",
"@xmemo/client@latest",
"xmemo-mcp"
]
}
}
}
Frequently asked questions
Celiums Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Memory Os Cli belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Celiums Memory for knowledge & memory work and Memory Os Cli for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Celiums Memory is listed as free. Auth: api key required. Memory Os Cli is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add celiums-celiums-memory and yonro-memory-os-cli as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Celiums Memory has a quality signal of 56/100 (Good) with 3 views, 0 installs and 23 GitHub stars. Memory Os Cli has 65/100 (Great) with 3 views, 0 installs and 12 GitHub stars.