code-context-mcp
Indexes codebase metadata into a SQLite database and provides tools for executing SQL queries and statements to manage and retrieve information about file dependencies, exports, and change history.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@code-context-mcpFind which files export the 'useAuth' hook"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
# Requires Node.js 22 or newer. Node.js 24 LTS is recommended.
npm install vlm-code-context-mcp
# The code index (default): 6 tools
npx code-context-reindex . --db ./context.db
claude mcp add code-context -- npx code-context ./context.db
# Or the sprint process instead: setup installs code-context-sprint, /kickoff, the dashboard
npx code-context-mcp setup .
npx code-context-dashboard ./context.db # optional: live dashboard on :3333# override the watch directory (4th argument)
npx code-context-dashboard ./context.db 3333 ./kickoffsearch_files("auth middleware") → find the right file
get_file_context("src/auth.ts") → understand role, exports, dependents
Read("src/auth.ts") → only now read the actual code# Simulated (no model, no cost)
pnpm run bench
# Agent (real model, real tokens; needs ZAI_API_KEY or DEEPSEEK_API_KEY)
pnpm run bench:live --provider glm
# Publish the run to the bench-results branch (rebuilds the site)
pnpm run bench:publish# The code index (default), after npm install
claude mcp add code-context -- npx code-context ./context.db
# Or the sprint process instead (same server name, same context.db; includes the code tools)
claude mcp add code-context -- npx code-context-sprint ./context.db
# Without a local install (the index)
claude mcp add code-context -- npx -y vlm-code-context-mcp ./context.db
# Add globally (the index; dist/server/sprint.js for the sprint process)
claude mcp add --scope user code-context node /path/to/node_modules/vlm-code-context-mcp/dist/server/index.js ./context.db
# Remove
claude mcp remove code-context# Profiles (default: code, 6 tools)
CODE_CONTEXT_PROFILE=full # 97 tools: the sprint process (setup writes it)
CODE_CONTEXT_PROFILE=all # 103 tools
CODE_CONTEXT_TOOLSETS=scrum # add toolsets: code-admin, scrum, fun, stream
# Output
OVERDRIVE_FLAIR=0 # flair off (1 forces it on)
CODE_CONTEXT_TIMESTAMPS=1 # add modified/indexed timestamps
CODE_CONTEXT_ABSOLUTE_PATHS=1 # absolute paths
# Skills
CODE_CONTEXT_SKILLS_AUTOSYNC=1 # sync skills from upstream at boot# Contributors use pnpm (pnpm-lock.yaml); install once
pnpm install
# MCP server
pnpm run dev
# Dashboard (Vite dev server with HMR)
pnpm run dashboard:dev
# Tests
pnpm test # backend
pnpm run test:all # backend + frontend
# Maintainers: publish to the npm registry (runs prepublishOnly = pnpm run build)
pnpm publishThis server cannot be deployed
Maintenance
Related MCP Connectors
Coding agents in multi-service codebases routinely rebuild existing helpers, trust stale type definitions, and modify API contracts without knowing who consumes them. Carrick solves this by indexing your entire TypeScript ecosystem across service and repository boundaries. By integrating deeply with the TypeScript compiler, Carrick traces every route, type, and cross-service call while recording function behaviour so agents search by intent rather than name. Delivered via MCP for AI agents and LSP for IDEs, Carrick ensures models see existing endpoints and utilities before generating new code. The scanner is source-available and runs from your CLI or CI pipeline.
Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.
Repository knowledge graph MCP server for codebase understanding and debugging.
Hosted code graph over MCP: exact callers, dependencies, and cross-repo blast radius for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides code intelligence by indexing source code into SQLite and offering MCP tools for symbol search, flow tracing, and context retrieval to assist with code navigation and understanding.-
- AlicenseBqualityDmaintenanceAn MCP server that indexes source code into a local database and provides tools for querying code symbols, dependencies, and tree structure for JavaScript/TypeScript, Java, and Python.7MIT
- AlicenseAqualityCmaintenanceIndexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.722 npmMIT
- FlicenseAqualityBmaintenanceMCP server that indexes TypeScript/React project symbols in memory, enabling agents to find definitions, references, and dependencies without reading the whole repo. Also includes a local visual dashboard with no outbound network calls.10-