ContextCache MCP
A local MCP server that indexes TypeScript/JavaScript projects and returns budget-aware, dependency-optimized context packs for AI coding assistants.
README
ContextCache MCP
Budget-aware context packs for AI coding assistants.
Stop sending entire codebases to your LLM. Send only what matters — within a token budget you control.
ContextCache is a local MCP server that indexes your TypeScript/JavaScript project and returns Context Packs — minimal, dependency-aware file sets optimized for a specific task.
Works with Cursor, Claude Code, Codex CLI, and any MCP-compatible client.
Why use ContextCache?
| Without ContextCache | With ContextCache |
|---|---|
| AI reads 200–500 files blindly | AI receives 5–15 ranked files |
| 50k+ tokens per request | 2k–8k tokens within your budget |
Misses UserRepository.ts behind AuthService.ts |
Dependency graph expands related files |
| No visibility into context cost | token_metrics + relevance_score on every pack |
Example: task "fix login bug" on a 500-file repo → returns AuthService.ts, JwtMiddleware.ts, and their dependencies — not your entire src/ tree.
Features
- Budget-aware selection — set
budget_tokens; engine stops before exceeding it - Dependency graph — BFS expansion from seed files (not flat keyword search)
- AST-based indexing — TypeScript Compiler API extracts classes, functions, imports, exports
- Incremental index — skips unchanged files via
content_hash - Query cache — instant responses for repeated tasks (auto-invalidated on reindex)
- Relevance score — 0.0–1.0 signal strength on every pack
- 100% local — SQLite on disk, no cloud, no API keys, no embeddings required
- Two MCP tools —
get_context_pack,get_file_summary
Quick start
Prerequisites
- Node.js 20+
- A TypeScript or JavaScript project to index
1. Clone & build
git clone https://github.com/YOUR_USERNAME/contextcache-mcp.git
cd contextcache-mcp
npm install
npm run build
2. Index your project
# From your project root:
node /path/to/contextcache-mcp/apps/indexer/dist/cli.js init
node /path/to/contextcache-mcp/apps/indexer/dist/cli.js index
node /path/to/contextcache-mcp/apps/indexer/dist/cli.js stats
3. Add MCP server to your AI client
Cursor — create or edit .cursor/mcp.json in your project:
{
"mcpServers": {
"contextcache": {
"command": "node",
"args": ["/absolute/path/to/contextcache-mcp/apps/server/dist/index.js"],
"env": {
"CONTEXTCACHE_ROOT": "${workspaceFolder}"
}
}
}
}
Claude Desktop — edit claude_desktop_config.json with the same block.
See mcp-config.example.json for a template.
4. Use it
Ask your assistant to call get_context_pack at the start of a coding task:
{
"task": "fix authentication bug in login flow",
"budget_tokens": 4000,
"mode": "cursor"
}
Sample response:
{
"relevance_score": 0.84,
"budget_used": 2300,
"budget_remaining": 1700,
"summary": "3 core files, 2 dependencies via graph.",
"files": [
{
"path": "src/auth/AuthService.ts",
"score": 0.92,
"summary": "Classes: AuthService. Exports: login, authenticate",
"token_estimate": 340
}
],
"dependencies": [
{ "path": "src/repos/UserRepository.ts", "relation": "imported_by", "depth": 1 }
],
"token_metrics": {
"full_project_tokens": 58000,
"selected_tokens": 2300,
"saved_tokens": 55700,
"reduction_percent": 96.0
}
}
MCP tools
get_context_pack
Builds a complete context pack for a task.
| Parameter | Type | Default | Description |
|---|---|---|---|
task |
string |
required | What you want to accomplish |
budget_tokens |
number |
8000 |
Maximum tokens for the pack |
mode |
"json" | "text" | "cursor" |
"json" |
text/cursor returns markdown |
use_snapshot |
boolean |
false |
Compare against manual snapshot baseline |
skip_cache |
boolean |
false |
Bypass query cache |
get_file_summary
Returns structured metadata for a single file.
{ "path": "src/auth/AuthService.ts" }
CLI
npm run contextcache -- <command>
| Command | Description |
|---|---|
init [path] |
Create .contextcache/ in a project |
index [paths...] |
Index TS/JS files (incremental) |
stats |
Index stats, token totals, relevance averages |
snapshot |
Save a manual baseline snapshot |
pack <task> |
Generate a context pack from terminal |
# Human-readable pack
npm run contextcache -- pack "fix login bug" -b 4000 -m text
# JSON pack
npm run contextcache -- pack "fix login bug" -b 4000 -m json
How it works
Your task + budget_tokens
│
▼
QueryCache ── hit? ──► return cached pack
│ miss
▼
HeuristicRanker ──► rank files by symbols, paths, imports
│
▼
DependencyGraph ──► expand related files (BFS, 2 hops)
│
▼
TokenBudgetManager ──► select files until budget is full
│
▼
Context Pack + relevance_score + token_metrics
Ranking signals: symbol match · path match · graph proximity · import match
Benchmarks
npm run benchmark
npm run benchmark:report # saves benchmarks/results/latest.json
Tracks relevance_score, precision, reduction_percent, and generation_time_ms against fixture projects.
Project structure
contextcache-mcp/
├── apps/
│ ├── shared/ # ContextEngine, DependencyGraph, indexer
│ ├── indexer/ # CLI (contextcache)
│ └── server/ # MCP server (stdio)
├── benchmarks/
├── mcp-config.example.json
└── ARCHITECTURE.md
Each indexed project gets a .contextcache/ folder:
your-project/.contextcache/
├── config.json
└── contextcache.db
What it is NOT
- Not a RAG / vector search tool
- Not a cloud service
- Not a flat file finder — it builds coherent packs via dependency graph
- Not dependent on paid embedding APIs (MVP)
Roadmap
- [ ] Python & C# parsers (tree-sitter)
- [ ] Optional semantic search (local embeddings)
- [ ]
get_related_filestool - [ ] npm global install (
npx contextcache)
Requirements
| Requirement | Version |
|---|---|
| Node.js | 20+ |
| Languages (MVP) | TypeScript, JavaScript |
Contributing
Issues and PRs welcome. See ARCHITECTURE.md for technical details.
- Fork the repo
- Create a branch (
git checkout -b feature/my-feature) - Run
npm run build && npm run benchmark - Open a PR
License
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.