Cozo Memory vs Cognee
A side-by-side look at the Cozo Memory and Cognee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cozo Memory for knowledge & memory work as a local process; choose Cognee 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 Cozo Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EMBEDDING_MODEL. - You want tools like
mutate_memory, query_memory, analyze_graph.
Choose Cognee when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 51/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EMBEDDING_MODEL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 32,497 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View Cozo Memory | View Cognee |
Tools & capabilities
Cozo Memory tools 5
mutate_memoryWrite operationsquery_memoryRead operationsanalyze_graphGraph analysismanage_systemMaintenanceedit_user_profileUser preferences
Cognee tools
No tool names declared yet. Check the project README from 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.
Cozo Memory
{
"mcpServers": {
"cozo-memory": {
"command": "npx",
"args": [
"-y",
"cozo-memory"
],
"env": {
"EMBEDDING_MODEL": "YOUR_EMBEDDING_MODEL_HERE"
}
}
}
}
Cognee
{
"mcpServers": {
"topoteretes-cognee": {
"command": "uvx",
"args": [
"cognee"
]
}
}
}
Frequently asked questions
Cozo Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Cognee belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Cozo Memory for knowledge & memory work and Cognee 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.
Cozo Memory has no declared pricing — check the project's own site. Cognee is listed as free. Auth: no auth required. 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 cozo-memory and topoteretes-cognee as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cozo Memory has a quality signal of 51/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Cognee has 55/100 (Good) with 5 views, 0 installs and 32,497 GitHub stars.