mcpField
C
context-sync

context-sync

Local
github.com/Intina47Memory & Knowledge189Updated 29w ago
Repository

About context-sync

Context Sync is a local-first MCP server that gives AI coding tools a persistent memory of a codebase, including project identity, decisions, and active work. It is aimed at developers who work across several AI coding clients and need sessions to continue smoothly.

Key features

  1. 01Persistent project context storage
  2. 02Decision and constraint recording and recall
  3. 03Structured file exploration and search
  4. 04Git-aware context and analysis
  5. 05Optional read-only Notion lookup
  6. 06Git hooks for automatic context capture

Use cases

  1. 01Restore project background at the start of a new session
  2. 02Record architectural decisions for later sessions
  3. 03Share one project memory across several AI coding tools

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "intina47-context-sync": {
      "command": "npx",
      "args": [
        "-y",
        "@context-sync/server"
      ]
    }
  }
}
Run commandnpx -y @context-sync/server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@context-sync/server1.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Context Sync

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

What It Does

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

Install

Install 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.

Verify

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.

Optional Notion Setup

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: "..." })

First-Time Workflow

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

Git Integration

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

Data And Config

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.

Supported Platforms

  • Claude Desktop
  • Cursor
  • VS Code + GitHub Copilot
  • Continue.dev
  • Zed
  • Windsurf
  • Codeium
  • TabNine
  • Codex CLI
  • Claude Code
  • Antigravity

Docs

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.