MCP AutoMem vs Cognee
A side-by-side look at the MCP AutoMem 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 MCP AutoMem for knowledge & memory work; 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 MCP AutoMem when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You have the keys it needs:
AUTOMEM_API_URL, AUTOMEM_API_KEY.
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 | 40/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | AUTOMEM_API_URLAUTOMEM_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 65 | 32,581 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCP AutoMem | View Cognee |
Tools & capabilities
MCP AutoMem tools
No tool names declared yet. Check the project README from the listing page.
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.
MCP AutoMem
No confirmed install command for MCP AutoMem yet — follow the setup steps linked from its listing page rather than a guessed package name.
Cognee
{
"mcpServers": {
"topoteretes-cognee": {
"command": "uvx",
"args": [
"cognee"
]
}
}
}
Frequently asked questions
MCP AutoMem is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Cognee belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP AutoMem 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. MCP AutoMem has no confirmed install command yet — follow its own setup instructions.
MCP AutoMem is listed as free. 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 mcp-automem and topoteretes-cognee as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP AutoMem has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 65 GitHub stars. Cognee has 55/100 (Good) with 5 views, 0 installs and 32,581 GitHub stars.