Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Benchmark AI models on real prompts. Find cheaper, faster alternatives across 340+ models.
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.
LLMTEST_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"llmtest": {
"command": "npx",
"args": [
"-y",
"llmtest-mcp"
],
"env": {
"LLMTEST_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add llmtest --env LLMTEST_API_KEY=your-value -- npx -y llmtest-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"llmtest": {
"command": "npx",
"args": [
"-y",
"llmtest-mcp"
],
"env": {
"LLMTEST_API_KEY": "your-value"
}
}
}
}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": {
"llmtest": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"llmtest-mcp"
],
"env": {
"LLMTEST_API_KEY": "your-value"
}
}
}
}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 7, 2026
The registry name was verified with the GitHub account tjacquesson, which owns the repo
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 1 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.
You need to fill in: LLMTEST_API_KEY
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.6.1) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
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.
MCP server that benchmarks AI models on your actual prompts and finds cheaper, faster alternatives. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible tool.
Sign up at llmtest.io and grab your API key from the dashboard.
Claude Code:
claude mcp add llmtest -- npx llmtest-mcp
Then set your key:
export LLMTEST_API_KEY=llmt_your_key_here
Cursor / Windsurf / Other MCP clients:
Add to your MCP config file:
{
"mcpServers": { "llmtest": { "command": "npx", "args": ["llmtest-mcp"], "env": { "LLMTEST_API_KEY": "llmt_your_key_here" } } } }
Just ask in natural language:
LLMTest is a proxy that sits between your app and AI providers. Point your app at https://llmtest.io/v1 instead of calling OpenAI/Anthropic directly, and LLMTest tracks your usage, benchmarks alternatives, and suggests cost savings.
This MCP server gives your AI assistant access to LLMTest's tools so it can manage everything for you.
| Tool | Description |
|---|---|
status | Show proxy status and activity summary |
list_flows | List all AI flows with cost and latency stats |
get_suggestions | Get pending model-switch recommendations |
update_suggestion | Accept or dismiss a suggestion |
run_benchmark | Benchmark a flow against challenger models |
optimize_prompt | Rewrite a flow's prompt and find a cheaper model that still works |
seed_samples | Add test prompts for pre-launch benchmarking |
list_samples | Show stored test samples per flow |
list_new_models | Show new and trending models |
get_account | Check credit balance and usage |
get_autopilot_status | Check whether autopilot is on and whether the account is eligible |
enable_autopilot | Turn on weekly auto-optimization with safety gates + drift-based auto-revert |
disable_autopilot | Turn off autopilot (existing optimizations stay active) |
list_active_optimizations | List auto-accepted optimizations still inside their 24h revert window |
revert_optimization | Roll an auto-accepted optimization back to the previous prompt |
Autopilot automatically optimizes your flows on a weekly cadence. Changes that pass every safety gate go live with a 24-hour revert window. Drift detection keeps checking after that and rolls back if quality slips.
To enable from your IDE: ask your AI assistant something like "enable LLMTest autopilot". It will call enable_autopilot. Use get_autopilot_status to confirm prerequisites.
Prerequisites (checked per flow each cycle):
Safety gates (all must pass for auto-accept): 95% CI lower bound > 50% win rate, multi-judge agreement ≥ 80%, ≥ 20% total savings, no length-bias warning, golden-set regression check.
Revert: 24h window after auto-accept. After that, only drift detection can roll back.
Pre-launch (no traffic yet):
seed_samplesrun_benchmark to compare modelsget_suggestions with cheaper alternativesPost-launch (with real traffic):
https://llmtest.io/v1| Variable | Required | Description |
|---|---|---|
LLMTEST_API_KEY | Yes | Your API key from llmtest.io/dashboard |
LLMTEST_BASE_URL | No | Custom API URL (defaults to https://llmtest.io) |
MIT