Provides Git integration to support a persistent, versioned memory layer that tracks project context and decision history.
Enables AI models to read from and write directly to Notion workspaces, allowing them to pull project specifications and export feature documentation, architecture decisions, and plans.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Context Sync save this architecture decision to my Notion project docs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local-first project memory for AI coding tools over MCP.
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
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_project
remember
recall
read_file
search
structure
git
notion
Related MCP server: Doclea MCP
Install globally:
npm install -g @context-sync/serverAuto-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:
Claude Desktop: open the tools list
Cursor: open the tools list
VS Code / Copilot Chat Agent mode: check tools
Continue.dev: open the Continue panel
Codex CLI: codex mcp list
Claude Code: claude mcp list
If auto-config fails, use docs/TROUBLESHOOTING.md and docs/CONFIG.md.
Run the setup wizard if you want Notion integration:
context-sync-setupor:
npx context-sync-setupNotion 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 start
recall to recover context
structure and search to explore
read_file for focused inspection
remember when something should survive the current session
When you run set_project inside a git repository, Context Sync can install hooks for automatic context capture.
Installed hooks:
post-commit
pre-push
post-merge
post-checkout
Hooks are marked with Context Sync Auto-Hook, and existing hooks are backed up first.
The git tool supports:
status
context
hotspots
coupling
blame
analysis
Default locations:
Database: ~/.context-sync/data.db
Config: ~/.context-sync/config.json
Install status: ~/.context-sync/install-status.json
Custom database options:
CLI: context-sync --db-path /absolute/path/to/db
Env var: CONTEXT_SYNC_DB_PATH
See docs/DATA.md for storage details.
Claude Desktop
Cursor
VS Code + GitHub Copilot
Continue.dev
Zed
Windsurf
Codeium
TabNine
Codex CLI
Claude Code
Antigravity
This server cannot be deployed
Shared project memory that keeps teammates and AI agents aligned across sessions.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Memory for AI agent teams across tools, sessions, repositories, and teammates.
XMemo is a user-owned Memory OS for AI agents, providing a shared, persistent memory layer across AI assistants, IDEs, CLIs, tools, projects, and sessions. It enables ChatGPT, Claude, Codex, Cursor, Gemini, and other supported AI clients to access authorized long-term context without requiring users to repeatedly explain their preferences, project decisions, or previous work. Beyond basic memory storage and retrieval, XMemo supports semantic search, contextual recall, memory updates and corrections, source attribution, version history, project-scoped context, task tracking, and governed memory lifecycle management. Identity-aware access controls, scoped authorization, and memory isolation help users manage which agents and workflows can access their information. XMemo also provides advanced capabilities for structured knowledge, reusable procedures, and memory consolidation through its broader Memory OS platform. Connect through hosted MCP with OAuth or bearer-token authentication, or integrate directly through REST APIs and supported client tools. Memory remains available across authorized clients and sessions, with user-controlled access, export, and deletion. Website: https://xmemo.dev Documentation: https://xmemo.dev/docs
