mcp-dev-toolbox

# mcp-dev-toolbox **Ask your AI agent about your codebase in plain English — and get answers grounded in your actual code and git history.**  [](LICENSE)    An MCP server for Claude Desktop, Claude Code, Cursor and any other MCP client. Its headline feature is **local semantic code search**: find code *by meaning* ("where do we validate auth tokens?") using on-device embeddings — no API key, no code leaving your machine. Alongside it you get git history, diffs, blame, file inspection, and ready-made prompts for code review and commit messages. ### Why use it - 🔍 **Semantic search, fully local** — `all-MiniLM-L6-v2` embeddings indexed per function/class, stored on disk, no external API calls. - 🕰️ **Git-aware** — the agent can read log, diff, status and blame instead of guessing what changed. - 🔒 **Sandboxed by design** — every path is confined to `WORKSPACE_ROOT`; git runs without a shell. - 🧩 **Uses the whole MCP spec** — 12 tools, 3 resources and 4 prompts, not just tools. - ☁️ **Local or cloud** — stdio for desktop clients, SSE + Dockerfile for one-click Railway deploys. ### Quick start ```bash git clone https://github.com/walter789/MCP-dev-toolbox.git cd MCP-dev-toolbox pip install -r requirements.txt ``` Then point your MCP client at `server.py` with `WORKSPACE_ROOT` set to the project you want to explore (full config below), and ask: > *"Build the index, then find where we handle database connection errors."* --- ## Features | Primitive | Count | What's included | |-----------|-------|-----------------| | **Tools** | 12 | Git history, diffs, blame · File search, TODO finder, st…