MIMRY vs Context Sync
A side-by-side look at the MIMRY and Context Sync MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MIMRYKnowledge & Memory · Local subprocess (stdio)Local repo memory for coding agents: ranked files, context packs and a code graph for any task.40FairAuth: not declaredVerdict: choose MIMRY for knowledge & memory work as a local process; choose Context Sync 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?
MChoose MIMRY when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Context Sync 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 have the keys it needs:
CONTEXT_SYNC_DB_PATH.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MIMRY | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 40/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | CONTEXT_SYNC_DB_PATH |
| Verified owner | Community listing |
Tools & capabilities
MIMRY tools
No tool names declared yet. Check the project README from the listing page.
Context Sync 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.
MIMRY
{
"mcpServers": {
"mimry": {
"command": "uvx",
"args": [
"mimry"
]
}
}
}
Context Sync
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": [
"-y",
"context-sync-setup"
],
"env": {
"CONTEXT_SYNC_DB_PATH": "YOUR_CONTEXT_SYNC_DB_PATH_HERE"
}
}
}
}
Frequently asked questions
MIMRY is categorized under Knowledge & Memory and uses a local stdio subprocess. Context Sync belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MIMRY for knowledge & memory work and Context Sync 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.
MIMRY has no declared pricing — check the project's own site. Context Sync 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 mimry and context-sync as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MIMRY has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Context Sync has 47/100 (Fair) with 4 views, 0 installs and 190 GitHub stars.
