Callimachus vs Mnemos
A side-by-side look at the Callimachus and Mnemos MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Callimachus for knowledge & memory work as a local process; choose Mnemos 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 Callimachus 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.
Choose Mnemos 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.
- You want tools like
mnemos_store, mnemos_search, mnemos_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 45 | 23 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View Callimachus | View Mnemos |
Tools & capabilities
Callimachus tools
No tool names declared yet. Check the project README from the listing page.
Mnemos tools 9
mnemos_storeStore a memory (full auto-pipeline runs transparently)mnemos_searchHybrid FTS + semantic + file-overlap searchmnemos_contextAssemble budget-aware, MMR-diversified contextmnemos_getFetch by IDmnemos_updateUpdate content, summary, or tagsmnemos_deleteSoft-delete (recoverable via maintain)mnemos_relateLink two memories (supersedes, caused_by, depends_on)mnemos_maintainRun decay, archival, GC, stale detectionmnemos_runtimeReport live MCP server version, host, pid, executable, uptime, data dir, and project scope
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.
Callimachus
{
"mcpServers": {
"betabots-llc-callimachus": {
"command": "npx",
"args": [
"-y",
"callimachus-mcp"
]
}
}
}
Mnemos
{
"mcpServers": {
"s60yucca-mnemos": {
"command": "npx",
"args": [
"-y",
"@s60yucca/mnemos"
]
}
}
}
Frequently asked questions
Callimachus is categorized under Knowledge & Memory and uses a local stdio subprocess. Mnemos belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Callimachus for knowledge & memory work and Mnemos 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.
Callimachus is listed as free. Auth: no auth required. Mnemos 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 betabots-llc-callimachus and s60yucca-mnemos as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Callimachus has a quality signal of 57/100 (Good) with 5 views, 0 installs and 45 GitHub stars. Mnemos has 59/100 (Good) with 2 views, 0 installs and 23 GitHub stars.