MCP server for code context from local git repositories
MCP server for code context from local git repositories. The code context mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
better-sqlite3 on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
queryRepo — Clones a repository, processes code, and performs semantic search:This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Code Context MCP's toolset — queryRepo — is a fair guide to whether it matches your workflow. It is maintained by fkesheh; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| queryRepo | Clones a repository, processes code, and performs semantic search: |
{
"mcpServers": {
"code-context": {
"command": "npx",
"args": ["-y", "better-sqlite3"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.