Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Compiler-backed code intelligence: calls, data flow, references and class hierarchy as tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"benzi": {
"command": "uvx",
"args": [
"benzi-mcp"
]
}
}
}Run this in your terminal
claude mcp add benzi -- uvx benzi-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"benzi": {
"command": "uvx",
"args": [
"benzi-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"benzi": {
"type": "stdio",
"command": "uvx",
"args": [
"benzi-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The publisher (varianttech.net) is not the repo owner (oooscoos); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.7) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Language Agnostic · Model Agnostic · Compiles Locally · BYOK · MCP Compatible
— What is Benzi —
— Live demos —
— Language support —
— Getting started —
— SWE-bench Verified —
— How it works —
— Toolset —
— Features —
— Benzi vs CC, DSH, OC —
— FAQ and Benzi's map vs LSP/SCIP indexers —
Most AI coding agents grep and glob raw source code into AI model's context window and hope the model finds what matters. Benzi parses every file first — a real compiler, built on tree-sitter — into a precise, queryable map. Every symbol, every call edge, every reference, every class in its inheritance chain. One pass, done.
Every file parsed, imports resolved, class ancestry built, every identifier traced to its definition — before a single question is answered. Call flow and data flow join at every call site, so a bad value traces to its origin in one tool call. Claude Code greps; Cursor embeds; Aider maps signatures; Benzi resolves — in O(1). Ten languages so far, plus a markup engine for HTML, CSS, and DOM-JS — see Language support. Benzi is free to use during beta.
You can try pasting this repo's link to Benzi in the live demo too!
Benzi on SQLite
Like where this is headed? A ⭐ goes a long way.
[StallionSwipe](BENZI_GREENFIELDING_EXAMPLES/horse_tinder/) · Python, HTML, CSS, JS — a dating app for horses, greenfielded by Benzi from scratch in a single chat session. No image is a file: every horse portrait is procedural SVG, generated in code. Match with one and it flirts back through a real model, live. Frontend, backend, and the prompts — all written by Benzi. Try it live.
Or, try any repo of your choice at all here — point Benzi at any public GitHub repo and it builds the index live. varianttech.net/demo.
Python · JavaScript · TypeScript · Java · C# · C++ · C · Go · Rust · Ruby
One compiler, ten languages — each is a tree-sitter grammar plugin, so the core of the map (symbols, call edges, references, inheritance, data flow) is built the same way everywhere.
Depth is uneven. Python is deepest, and the only one with the runtime tracer. Every language reaches the core of the map, but each has its own constructs, not all modelled yet. For most code, every other language's map comes close to Python's.
Incremental reindexing is also less optimized for C, C++, Rust, and Ruby — it works, just not as fast on a large edit loop.
Wrong or thin answer in your language? Open an issue with the repo, the question, and what it got wrong — that's how the uneven parts get found.
Benzi is completely free to use during beta. There are two ways to use it, and they share one login: the same benzi-login config works everywhere.
BENZI_ESCALATE_MODEL=deepseek-pro (or another model alias) to turn it on.Run it either way:
The same steps as the VS Code extension, from your terminal: install, log in, set your model and key, then run.
bash pip install benzi
Python 3.11–3.14 on Windows, macOS and Linux. Installs the benzi-login, benzi-headless and benzi-mcp commands.
1. Log in — emails you a one-time code to type in.
bash benzi-login --login you@example.com
2. Set your model and key
bash benzi-login --model deepseek benzi-login --nonanthropic-key YOUR_KEY # or for Claude models: benzi-login --anthropic-key YOUR_KEY
3. Run it on a repo — from the terminal, for scripts and CI.
bash benzi-headless . "fix the failing test in parser.py"
The steps are the same as headless: pip install benzi, then log in with benzi-login. You can skip the model and key, because your own agent does the model calls. Then register benzi-mcp with your agent instead of running benzi-headless. For example, in Claude Code, once for all your projects:
claude mcp add --scope user benzi -- benzi-mcp
benzi-mcp then serves whichever folder you start Claude Code in, so switching projects needs nothing extra. To pin it to one repo no matter where you start, pass that repo's path:
claude mcp add --scope user benzi -- benzi-mcp /path/to/your/repo
VS Code's settings panel and benzi-login share one config: log in once, and VS Code, headless and MCP all use it.
The full SWE-bench Verified set — 500 real GitHub issues from twelve Python repositories — run end to end on DeepSeek V4.1-Flash, one attempt per instance, graded by the official swebench.harness.run_evaluation inside its own per-instance Docker images, with network access to GitHub and PyPI blocked inside every container. 413 of 500 resolved (82.6%) for $9.26 in total, 1.85¢ per task, with 97.6% of input tokens served from cache.
| Resolved | 413 / 500 (82.6%) |
| Attempts per instance | 1 (pass@1) |
| Model | DeepSeek V4.1-Flash, thinking mode at its default effort |
| Total generation cost, all 500 | $9.26 |
| Cost per task | $0.0185 |
| Model turns: total / median per instance | 13,281 / 20.5 |
| Input tokens served from prompt cache | 97.6% |
| Output tokens, total (of which reasoning) | 8.7M (6.2M) |
Full technical report: swebench-october-run2/SWE_BENCH_REPORT.md (web version). Every instance's cost, tokens and turns: varianttech.net/benchmark_swebench. The cross-harness efficiency comparison below (and the full 24-bug chart): varianttech.net/benchmark.
<img src="https://raw.githubusercont
Only the beginning is shown; read the rest in the repo