context-mcp
Provides persistent memory and a codebase knowledge graph for AI coding assistants, enabling shared context across multiple tools like Claude, Cursor, and ChatGPT, with significant token reduction.
README
<p align="center"> <img src="src/assests/main.png" alt="context-mcp" /> </p>
<p align="center"> <a href="https://www.npmjs.com/package/context-mcp-server"><img src="https://img.shields.io/npm/v/context-mcp-server?style=flat-square" alt="npm version" /></a> <a href="https://www.npmjs.com/package/context-mcp-server"><img src="https://img.shields.io/npm/dm/context-mcp-server?style=flat-square" alt="npm downloads" /></a> <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg?style=flat-square" alt="License: MIT" /></a> <a href="package.json"><img src="https://img.shields.io/node/v/context-mcp-server?style=flat-square" alt="Node.js" /></a> </p>
Persistent memory and codebase knowledge graph for AI coding assistants — delivered as a single MCP server.
One shared context store across Claude Code, Cursor, Gemini CLI, Codex, Windsurf, VS Code Copilot, Claude.ai, and ChatGPT. Save context from one AI, pick it up in another.
The Problem
Every conversation with an AI assistant starts from zero. The AI re-reads files it already read yesterday, re-discovers architecture it already understood, re-derives decisions that were already made. You repeat context. You paste the same background.
This gets worse as projects grow — reading 20 files to answer "what calls this function?" burns thousands of tokens every time.
What It Solves
- Persistent memory — decisions, bugs, notes, and config saved across sessions, loaded automatically at conversation start
- Shared store —
~/.context-mcp/projects/<name>/per-project on your machine; all AI tools read and write it - ContextGraph — build a knowledge graph of your codebase once, answer structural questions in ~500 tokens instead of ~50,000
Real measured reduction on this project: 162× fewer tokens, 99.38% reduction per conversation.
Installation
npm install -g context-mcp-server
Requires Node.js ≥ 18. Installs context-mcp, context-mcp-http, and the ctx CLI.
ContextGraph requires uv (Python runner). Memory tools work without it.
# macOS / Linux
curl -Ls https://astral.sh/uv/install.sh | sh
# Windows
winget install astral-sh.uv
Quick Start
Run from your project root:
ctx install --initial
This installs Node.js + Python (ContextGraph) dependencies. Run once after installing the npm package.
Then write MCP config + AI instruction files:
ctx install --all
To install for a specific platform only:
ctx install --claude # Claude Code
ctx install --cursor # Cursor
ctx install --vscode # VS Code Copilot
ctx install --gemini # Gemini CLI
ctx install --codex # Codex CLI
ctx install --windsurf # Windsurf
For web clients (Claude.ai, ChatGPT), start the HTTP server:
ctx online # start in background, prints OAuth credentials + URL
ctx online --restart # force restart
ctx online --port 3200 # different port
CLI Reference
Both ctx and context are aliases for the same CLI.
ctx # interactive mode (UI)
# Context
ctx list [project] # list entries by tree: graph / context / summary / plans
ctx projects # all projects with graph status + recent entries
ctx search "query" # keyword → semantic fallback search
ctx add # add entry interactively
ctx summary [project] # summarize recent entries
# Delete
ctx delete <id-prefix> # delete one entry
ctx delete project <name> # delete all entries for a project
# Server
ctx online # start HTTP server (idempotent)
ctx online --restart # force stop + restart
ctx settings # view and edit config interactively
# Tools
ctx benchmark # token savings report (memory + graph)
Security
File and git tools are sandboxed to your project root. Pass rootPath when calling context.resume:
{ "action": "resume", "project": "my-app", "rootPath": "/home/user/my-app" }
Any file or git operation outside that directory is rejected. Applies to all HTTP-connected clients.
Features
Memory
context.resume— loads recent entries, active plans, and graph status; registersrootPathfor sandboxingcontext.save— store context with 4 types:decision,bug,note,configcontext.get/context.update/context.delete— full CRUD, single or batchsearch— keyword-first, semantic fallbackplan— auto-triggered when AI makes any plan; saves a markdown summary to aplanDiryou specify- Auto-deduplication on save; auto-compact at 20 entries → stored in
summary.json
ContextGraph
Also called CodeGraph. MCP tools use the
codegraph_*prefix — both names mean the same thing.
Step 1 — Build (once per project, runs locally, no API cost):
codegraph_build(path)
Parses codebase via tree-sitter AST (16 languages, regex fallback). Extracts functions, classes, imports, call edges. Build metadata saved to ~/.context-mcp/projects/<name>/graph.json.
Step 2 — Query (instant, forever):
codegraph_query(path, question?, node?) → structural question OR single-node lookup (or both)
codegraph_path(path, from, to) → shortest path between two concepts
codegraph_nodes(path, type) → list all nodes of a type
codegraph_report(path) → god nodes, clusters, surprising connections
codegraph_query accepts question (natural language), node (exact/partial name for type + file + deps + callers), or both in one call. Use before reading any files.
File & Git Tools
Available to HTTP-connected clients (Claude.ai, ChatGPT). Local AI clients use their native IDE tools.
read_file,write_file,patch_file,create_dir,list_dir,delete_filegit_status,git_diff,git_log,git_add,git_commit,git_push,git_pull,git_branch,git_stash,git_reset,git_show
Enable git tools with --access-git flag or access_git: true in config.
Server Flags
context-mcp [--data-dir <path>]
context-mcp-http [--port <number>] [--host <string>] [--access-git] [--data-dir <path>]
Default port: 3100. Default data dir: ~/.context-mcp.
Config Reference
~/.context-mcp/contextconfig.json — auto-created on first run:
| Field | Default | Description |
|---|---|---|
client_id |
"context-mcp" |
OAuth client ID |
client_secret |
auto-generated | OAuth signing secret |
port |
3100 |
HTTP server port |
host |
"localhost" |
HTTP bind host |
access_git |
false |
Enable git tools for HTTP clients |
public_url |
null |
Public URL for ctx online output |
allowed_redirect_uris |
["https://claude.ai"] |
OAuth redirect URI whitelist |
allowed_origins |
[] |
Extra CORS origins |
Edit with ctx settings.
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.