Cerebro MCP server for ZCode — 17 memory tools. Auto-reads ~/.config/cerebro/config.json. Use via: npx -y @mingxy/cerebro-mcp-zcode
Cerebro MCP server for ZCode — 17 memory tools. Auto-reads ~/.config/cerebro/config.json. Use via: npx -y @mingxy/cerebro-mcp-zcode. That is what the cerebro mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Cerebro gives AI agents shared persistent memory — across sessions, devices, agents, and teams. One API key reconnects everything. Self-hosted, open-source.
The server publishes 14 tools. What each one is for:
Concept — What it ismemory_store — Save facts, decisions, preferences with smart dedupmemory_search — 11-stage hybrid search (vector + BM25 + reranker)memory_get — Retrieve a specific memory by IDmemory_update — Modify content, tags, importance, tiermemory_delete — Remove a memorymemory_list — Browse memories with filters and paginationmemory_ingest — Smart-ingest full conversations (LLM extraction)memory_profile — Auto-generated user profile (static facts + dynamic context)memory_stats — Analytics: tag distribution, decay curves, relation graphsspace_create — Create Team or Organization spacesspace_list — List all accessible spacesConfiguration is passed through the environment: OMEM_API_URL, OMEM_API_KEY, OMEM_EMBED_API_KEY, AWS_ENDPOINT_URL, OSS_ACCESS_KEY_ID, OSS_ACCESS_KEY_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cerebro's toolset — Concept, memory_store, memory_search and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mingxy; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Concept | What it is |
| memory_store | Save facts, decisions, preferences with smart dedup |
| memory_search | 11-stage hybrid search (vector + BM25 + reranker) |
| memory_get | Retrieve a specific memory by ID |
| memory_update | Modify content, tags, importance, tier |
| memory_delete | Remove a memory |
| memory_list | Browse memories with filters and pagination |
| memory_ingest | Smart-ingest full conversations (LLM extraction) |
| memory_profile | Auto-generated user profile (static facts + dynamic context) |
| memory_stats | Analytics: tag distribution, decay curves, relation graphs |
| space_create | Create Team or Organization spaces |
| space_list | List all accessible spaces |
| space_add_member | Invite users to a shared space |
| memory_share | Share a memory to any space with provenance |
{
"mcpServers": {
"cerebro": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"OMEM_API_URL": "your-value",
"OMEM_API_KEY": "your-value",
"OMEM_EMBED_API_KEY": "your-value",
"AWS_ENDPOINT_URL": "your-value",
"OSS_ACCESS_KEY_ID": "your-value",
"OSS_ACCESS_KEY_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OMEM_API_URL | Endpoint or connection string the server talks to. | Yes |
| OMEM_API_KEY | Credential the server authenticates with. | Yes |
| OMEM_EMBED_API_KEY | Credential the server authenticates with. | Yes |
| AWS_ENDPOINT_URL | Endpoint or connection string the server talks to. | Yes |
| OSS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| OSS_ACCESS_KEY_SECRET | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.