Context Sync

io.github.Intina47Published by GitHub account Intina47v1.0.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local-first project memory for AI coding tools: stores codebase context and makes it recallable across sessions and editors.

What you can do
  • Set the active project and recall stored context, decisions, constraints and caveats
  • Explore a codebase with structure listing, search and focused file reads
  • Record new memories that should survive the current session
  • Inspect git status, context, hotspots, coupling, blame and analysis
  • Optionally search and read Notion pages in read-only mode
When to use it
Useful when you work on the same codebase across many sessions or several AI coding tools and want decisions and project context to carry over instead of being re-explained. Also handy for structured codebase exploration and git-aware context.
Requirements
Runs locally as an npm package (@context-sync/server) over stdio; global install is needed for auto-configuration, otherwise manual MCP config is required. Node.js and a supported client such as Claude Desktop, Cursor, VS Code, Continue, Zed, Windsurf, Codex CLI or Claude Code. Optional Notion setup via a separate setup wizard. Data is stored by default in a local SQLite database under the user's home directory; the path can be changed with the CONTEXT_SYNC_DB_PATH environment variable.
Before you install
Installing globally runs auto-configuration that modifies AI tool settings. Setting a project inside a git repository can install post-commit, pre-push, post-merge and post-checkout hooks; existing hooks are backed up first, but review them before enabling. Memories, file contents and git data are written to a local database, and optional Notion access requires credentials from the setup wizard.

Installation

In SourceWeft

  1. Open Context Sync in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

bash
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:

bash
context-sync-setup

or:

bash
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:

text
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

Source: README.md at commit 235fd51

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts