Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @context-sync/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add io.github.intina47-context-sync -- npx -y @context-sync/server@1.0.1Execute em um terminal.
{ "mcpServers": { "io.github.intina47-context-sync": { "command": "npx", "args": [ "-y", "@context-sync/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Local-first project memory for AI coding tools over MCP.
Context Sync gives an agent a persistent memory layer for a codebase:
Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more
Context Sync is built for session continuity. Instead of relying on a model to remember earlier conversations, it stores the project context that matters and makes it retrievable through a small MCP tool surface.
The current core tools are:
set_projectrememberrecallread_filesearchstructuregitnotionInstall globally:
npm install -g @context-sync/server
Auto-configuration runs during global install. After install, restart your AI tool.
If you install locally instead of globally, auto-config does not run. Use the manual config guide in docs/CONFIG.md.
Check that context-sync appears in your MCP tool list:
codex mcp listclaude mcp listIf auto-config fails, use docs/TROUBLESHOOTING.md and docs/CONFIG.md.
Run the setup wizard if you want Notion integration:
context-sync-setup
or:
npx context-sync-setup
Notion support is intentionally read-only at the tool surface:
notion({ action: "search", query: "..." })notion({ action: "read", pageId: "..." })Start every new session by setting the project first:
1. set_project({ path: "/absolute/path/to/project" })
2. recall()
3. structure({ depth: 2 })
4. read_file({ path: "src/index.ts" })
5. remember({ type: "decision", content: "Use SQLite for local storage" })
Recommended pattern:
set_project once per project/session startrecall to recover contextstructure and search to exploreread_file for focused inspectionremember when something should survive the current sessionWhen you run set_project inside a git repository, Context Sync can install hooks for automatic context capture.
Installed hooks:
post-commitpre-pushpost-mergepost-checkoutHooks are marked with Context Sync Auto-Hook, and existing hooks are backed up first.
The git tool supports:
statuscontexthotspotscouplingblameanalysisDefault locations:
~/.context-sync/data.db~/.context-sync/config.json~/.context-sync/install-status.jsonCustom database options:
context-sync --db-path /absolute/path/to/dbCONTEXT_SYNC_DB_PATHSee docs/DATA.md for storage details.
Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more
{ "mcpServers": { "io.github.intina47-context-sync": { "command": "npx", "args": [ "-y", "@context-sync/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Context Sync roda localmente via stdio.
Última verificação: 2026-11-09. Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more