
Codebase Context Mcp
Give Claude Code or Cursor fast, local semantic search over your repo without sending the whole tree on every turn.
Overview
Codebase Context MCP is a Build-phase MCP server that indexes and searches your repository via WASM tree-sitter for agent-friendly codebase retrieval.
What is this MCP server?
- Indexes repositories with WASM tree-sitter for structure-aware parsing
- Search API over indexed symbols and chunks for agent tool calls
- Runs on ARM64 and x86_64 without native tree-sitter binaries
- Stdio MCP transport via npm package codebase-context-mcp (v1.0.1)
- Local-first context layer instead of re-uploading files each session
- Package version 1.0.1 on npm (identifier codebase-context-mcp)
- WASM tree-sitter indexing with ARM64 and x86_64 support
- Stdio transport per MCP server schema 2025-12-11
What problem does it solve?
Agents lose time and accuracy when they cannot reliably find the right files, types, and definitions across a growing repo.
Who is it for?
Indie developers on multi-package repos who want portable, local indexing on Apple Silicon or x86_64 Linux and macOS.
Skip if: Teams that only need single-file edits in tiny projects or who already use a managed cloud code search product they prefer not to duplicate.
What do I get? / Deliverables
After you register the server, agents can query a local index and pull structured context instead of guessing paths or pasting huge slices of the tree.
- Indexed workspace the agent can query via MCP tools
- Structure-aware search results for files and definitions
- Repeatable local context pipeline without cloud upload
Recommended MCP Servers
Journey fit
Indexing and retrieval sit in Build because they are how you wire agent context into day-to-day implementation, not a one-off launch or growth task. Agent-tooling is the canonical shelf for MCP servers whose main job is expanding what coding agents can see and query in the workspace.
How it compares
MCP codebase indexer, not a hosted documentation or static-analysis SaaS.
Common Questions / FAQ
Who is Codebase Context MCP for?
Solo and small-team builders who run AI coding agents daily and need fast, local search over their own repositories.
When should I use Codebase Context MCP?
Use it during Build when refactors, feature work, or debugging span many modules and @-file context is no longer enough.
How do I add Codebase Context MCP to my agent?
Install the npm package codebase-context-mcp, add a stdio MCP entry in Claude Code, Cursor, or Codex pointing at that command, then restart the client.