Context MCP Server

Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more

Local serverstdio

What is the Context MCP Server?

Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more

What you get

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

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
set_projectremember
recallread_file
searchstructure
post-commitpre-push
post-mergepost-checkout
statuscontext
hotspotscoupling
blameanalysis

How to install the Context MCP Server

{
  "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.

Configuration

VariableDescriptionRequired
CONTEXT_SYNC_DB_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • “Use Context to set project.”
  • “Use Context to recall.”
  • “Use Context to search.”

Frequently asked questions

Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.