Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more
Context MCP server exists for a simple reason — assistants are far more useful when they can act on Context directly instead of describing what you should do. Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more.
Context Sync gives an agent a persistent memory layer for a codebase: - project identity and tech stack - active work, decisions, constraints, and caveats - structured file exploration - git-aware context - optional read-only Notion lookup
Once Context is connected, these are the calls the assistant has available:
set_project — rememberrecall — read_filesearch — structureCursor — open the tools listContinue.dev — open the Continue panelpost-commit — pre-pushpost-merge — post-checkoutstatus — contexthotspots — couplingblame — analysisDatabase — ~/.context-sync/data.dbConfig — ~/.context-sync/config.jsonYou will need one environment variable: CONTEXT_SYNC_DB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at context-sync-setup on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Context's toolset — set_project, recall, search and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Intina47; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| set_project | remember |
| recall | read_file |
| search | structure |
| Cursor | open the tools list |
| Continue.dev | open the Continue panel |
| post-commit | pre-push |
| post-merge | post-checkout |
| status | context |
| hotspots | coupling |
| blame | analysis |
| Database | ~/.context-sync/data.db |
| Config | ~/.context-sync/config.json |
| CLI | context-sync --db-path /absolute/path/to/db |
| Windsurf | Codeium |
{
"mcpServers": {
"context-sync": {
"command": "npx",
"args": ["-y", "context-sync-setup"],
"env": {
"CONTEXT_SYNC_DB_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CONTEXT_SYNC_DB_PATH | Filesystem location the server is allowed to use. | Optional |
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.