developer-toolsai-memorymcpgitnotion
Stores project memory, code structure, file content, Git context, and optional read-only Notion data for AI coding sessions.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Configure Environment Variables (API Keys, Tokens, Options):
Add required secrets below — values are included directly in the generated snippet so you can copy and paste with confidence.
Quick Add:
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Recover project decisions at the start of a coding session
Explore a repository structure and inspect selected files
Track Git changes and repository hotspots
Share local project context across AI coding clients
Read selected Notion pages without write access
Key features
Local project memory over MCP
Structured file exploration
Git status and repository analysis
Optional read-only Notion lookup
Automatic Git context hooks
Configurable local database path
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Context Sync.
Extracted Tool Capabilities
Local project memory over MCP
Structured file exploration
Git status and repository analysis
Optional read-only Notion lookup
Automatic Git context hooks
Configurable local database path
How Context Sync works
What context-sync MCP server does
The context-sync MCP server provides a local memory layer for AI-assisted software development. It keeps project-specific information available across sessions, including the project identity, technology stack, current work, decisions, constraints, and caveats. This helps an agent recover relevant context after a new conversation or when switching between supported coding tools.
The server also exposes repository inspection capabilities. Agents can request a structured view of project files, read selected files, search project content, and query Git-related information. An optional Notion integration adds read-only search and page retrieval.
How it works
A session normally begins with set_project, which establishes the project path. The agent can then call recall to retrieve stored context, use structure and search to inspect the repository, and call read_file for focused file access. Information intended to persist beyond the current session is saved with remember, using categories such as decisions or other project context.
When the selected project is inside a Git repository, the server can install hooks for post-commit, pre-push, post-merge, and post-checkout. Existing hooks are backed up before installation, and the added hooks are marked with Context Sync Auto-Hook. Git analysis includes status, repository context, hotspots, coupling, blame, and general analysis actions.
The context-sync MCP server stores its database, configuration, and installation status under ~/.context-sync by default. A different database location can be selected through the command line or CONTEXT_SYNC_DB_PATH.
Setup and configuration
Install the package globally with npm:
Global installation performs automatic configuration. After installation, restart the AI coding application and verify that context-sync appears in its MCP tools. Local installation does not run the automatic configuration step, so it requires the manual configuration instructions referenced by the project.
Notion support is optional. Run context-sync-setup or npx context-sync-setup to configure it. The available Notion operations are limited to searching and reading pages; the provided material does not describe write operations.
Tools and capabilities
The listed MCP tools are:
set_projectfor selecting the active project.rememberfor saving durable project information.recallfor retrieving stored context.read_filefor focused file inspection.searchfor repository exploration.structurefor viewing the project layout.gitfor repository status and analysis actions.notionfor optional read-only Notion search and page reads.
Supported clients include Claude Desktop, Cursor, VS Code with GitHub Copilot, Continue.dev, Zed, Windsurf, Codeium, TabNine, Codex CLI, Claude Code, and Antigravity. The context-sync MCP server is therefore suited to workflows that move between multiple AI coding environments while keeping project context in a local store.
Limitations and notes
Notion access is read-only at the tool layer. Automatic configuration applies to global installation, while local installation requires manual setup. The server depends on the agent setting a project before repository-specific context can be recalled or explored. The provided material does not specify a license, authentication requirements, or remote hosting option.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
190
Stargazers on the source repository.
npm downloads
384
Package downloads in the last 30 days.
Last commit
5mo ago
Most recent push to the default branch.
Directory activity
3 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Context Sync
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/context-sync)HTML Embed
<a href="https://allmcps.com/mcp/context-sync"><img src="https://allmcps.com/api/badge/context-sync?style=directory" alt="Context Sync on AllMCPs" /></a>