Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Ask your AI agent why your tests are failing. Instant analysis on failures and regressions.
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.
TESULTS_API_TOKEN, TESULTS_READ_ONLYValues 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": {
"tesults": {
"command": "npx",
"args": [
"-y",
"tesults-mcp"
],
"env": {
"TESULTS_API_TOKEN": "your-value",
"TESULTS_READ_ONLY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add tesults --env TESULTS_API_TOKEN=your-value --env TESULTS_READ_ONLY=your-value -- npx -y tesults-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tesults": {
"command": "npx",
"args": [
"-y",
"tesults-mcp"
],
"env": {
"TESULTS_API_TOKEN": "your-value",
"TESULTS_READ_ONLY": "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": {
"tesults": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tesults-mcp"
],
"env": {
"TESULTS_API_TOKEN": "your-value",
"TESULTS_READ_ONLY": "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.
TESULTS_READ_ONLY envThese 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 tesults, 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: TESULTS_API_TOKEN
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 (1.1.0) reached the registry 14 days 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, MCP Server Autocad Lisp Helper
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.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
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.
Tesults MCP server. Connect AI agents and MCP-compatible tools to your Tesults test results, insights, and targets.
Full setup and usage documentation: https://www.tesults.com/docs/api/mcp
claude mcp add tesults-mcp npx tesults-mcp -e TESULTS_API_TOKEN=your-api-token
Set TESULTS_READ_ONLY=true in the MCP server's environment alongside TESULTS_API_TOKEN. This exposes only the seven reporting and insight tools. Target creation, editing, deletion and token regeneration are not registered, and non-GET API requests are blocked locally.
Existing configurations remain unchanged when this setting is omitted or false. This is a restriction in this MCP server, not a reduction in the API token's permissions. Keep the token private. Insight tools can still generate and cache AI analyses on the server; they do not change your test results or targets.
Requests time out after 60 seconds and responses are limited to 10 MiB. For large result sets, request fewer runs or use cases=false for summaries. API failures are returned as tool errors, not successful answers.
These options apply to this source version and require an updated installation once released. They do not change an already installed published package.
Run node --test tests/hardening.test.js. Tests do not call Tesults or use a real token.
MIT