Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Run AI-generated code safely. gVisor-isolated Python/JS sandboxes for any MCP client. Pay per run.
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.
CINCH_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": {
"cinch": {
"command": "npx",
"args": [
"-y",
"@cinch-codes/mcp"
],
"env": {
"CINCH_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cinch --env CINCH_API_KEY=your-value -- npx -y @cinch-codes/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cinch": {
"command": "npx",
"args": [
"-y",
"@cinch-codes/mcp"
],
"env": {
"CINCH_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": {
"cinch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cinch-codes/mcp"
],
"env": {
"CINCH_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 6, 2026
The registry name was verified with the GitHub account yusufkadry, 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: CINCH_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.1.1) reached the registry 4 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, Fomu MCP
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.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
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 for Cinch. Gives your AI assistant a real sandbox to run code in.
Without it, an assistant writes code and you run it yourself. With it, the assistant runs the code and reads the actual output — inside a gVisor-isolated container on Cinch's infrastructure, with no access to your machine, filesystem, or local network.
Pay per execution. No subscription floor.
Get an API key at cinch.codes, then add the server to your MCP client.
Claude Desktop — claude_desktop_config.json:
{
"mcpServers": { "cinch": { "command": "npx", "args": ["-y", "@cinch-codes/mcp"], "env": { "CINCH_API_KEY": "cinch_live_..." } } } }
Claude Desktop on Windows — same file, but Windows can't spawn npx directly, so wrap it with cmd /c:
{
"mcpServers": { "cinch": { "command": "cmd", "args": ["/c", "npx", "-y", "@cinch-codes/mcp"], "env": { "CINCH_API_KEY": "cinch_live_..." } } } }
Claude Code (macOS/Linux):
claude mcp add --scope user cinch -e CINCH_API_KEY=cinch_live_... -- npx -y @cinch-codes/mcp
Claude Code (Windows):
claude mcp add --scope user cinch -e CINCH_API_KEY=cinch_live_... -- cmd /c npx -y @cinch-codes/mcp
Cursor — .cursor/mcp.json, same shape as the Claude Desktop config above.
Restart the client. That's it — no install step, npx fetches it on first run.
execute_codeRuns a self-contained Python or JavaScript program and returns stdout, stderr, exit code, and duration.
| Parameter | Type | Default | Description | |
|---|---|---|---|---|
code | string | — | The complete program to run. Must print to stdout to return anything. | |
language | python \ | javascript | python | Runtime to execute in. |
Each call gets a clean sandbox. State does not persist between calls, so every snippet needs to stand on its own.
Deliberately minimal. Worth knowing before you wonder why an import failed:
| Runtimes | Python 3.12, Node 20 |
| Packages | Standard library only. No pip or npm packages are installed, and none can be installed at runtime. |
| Network | None. HTTP, DNS, and package installs all fail. |
| Filesystem | Root is read-only. /tmp is writable (64 MB) and destroyed when the run ends. |
| Memory | 256 MB |
| CPU | 0.5 cores |
| Time limit | 10 seconds |
| Isolation | gVisor (runsc), all capabilities dropped, no-new-privileges, non-root user, 64-process cap |
The tool description tells the model all of this up front, so it writes stdlib-only code instead of reaching for numpy and failing on the first call.
| Variable | Required | Default | Description |
|---|---|---|---|
CINCH_API_KEY | yes | — | Your Cinch API key. |
CINCH_TIMEOUT_MS | no | 20000 | Client-side timeout in ms. The API caps execution at 10s regardless. |
CINCH_BASE_URL | no | https://api.cinch.codes | Override the API endpoint. |
Windows: "Failed to connect" in `claude mcp list` — you're missing the cmd /c wrapper. Windows resolves npx to a batch script that can't be spawned directly; re-add the server using the Windows command above.
Windows: `npm error ENOENT ... AppData\Roaming\npm` — some Node installs never create npm's global folder, and npx refuses to run without it. Create it once and retry:
mkdir %APPDATA%\npm
Server exits immediately with "CINCH_API_KEY is not set" — the env var didn't reach the server. In Claude Code, put -e CINCH_API_KEY=... *before* the server name in claude mcp add. In config files, check the env block is inside the cinch entry.
Debugging any connection failure — run the server directly to see the real error instead of a generic status:
CINCH_API_KEY=cinch_live_... npx -y @cinch-codes/mcp # macOS/Linux
set CINCH_API_KEY=cinch_live_... && cmd /c npx -y @cinch-codes/mcp # Windows
Correct behavior is cinch-mcp ... ready followed by silence — an MCP server waits for a client. Anything else printed is the actual failure.
Code written by a model is untrusted code — nothing reviewed it before it ran. Executing it directly on your machine means handing it your filesystem, your network, and your credentials. Cinch runs it somewhere else entirely, in a disposable container with kernel-level isolation, and sends back only the output.
@cinch-codes/pangolinpangolin-sdkMIT