Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Single exec tool running caller Python in a network-isolated locked-down sandbox.
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.
MCP_EXEC_TRANSPORT, MCP_EXEC_DEFAULT_TIMEOUT_S, MCP_EXEC_MAX_TIMEOUT_S, MCP_EXEC_MAX_OUTPUT_BYTES, MCP_EXEC_MAX_STDIN_BYTES, MCP_EXEC_AUTH_TOKENValues 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": {
"exec": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_EXEC_TRANSPORT",
"-e",
"MCP_EXEC_DEFAULT_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_OUTPUT_BYTES",
"-e",
"MCP_EXEC_MAX_STDIN_BYTES",
"-e",
"MCP_EXEC_AUTH_TOKEN",
"docker.io/idconstruct/mcp-exec:v0.5.4"
],
"env": {
"MCP_EXEC_TRANSPORT": "your-value",
"MCP_EXEC_DEFAULT_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_OUTPUT_BYTES": "your-value",
"MCP_EXEC_MAX_STDIN_BYTES": "your-value",
"MCP_EXEC_AUTH_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add exec --env MCP_EXEC_TRANSPORT=your-value --env MCP_EXEC_DEFAULT_TIMEOUT_S=your-value --env MCP_EXEC_MAX_TIMEOUT_S=your-value --env MCP_EXEC_MAX_OUTPUT_BYTES=your-value --env MCP_EXEC_MAX_STDIN_BYTES=your-value --env MCP_EXEC_AUTH_TOKEN=your-value -- docker run -i --rm -e MCP_EXEC_TRANSPORT -e MCP_EXEC_DEFAULT_TIMEOUT_S -e MCP_EXEC_MAX_TIMEOUT_S -e MCP_EXEC_MAX_OUTPUT_BYTES -e MCP_EXEC_MAX_STDIN_BYTES -e MCP_EXEC_AUTH_TOKEN docker.io/idconstruct/mcp-exec:v0.5.4Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"exec": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_EXEC_TRANSPORT",
"-e",
"MCP_EXEC_DEFAULT_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_OUTPUT_BYTES",
"-e",
"MCP_EXEC_MAX_STDIN_BYTES",
"-e",
"MCP_EXEC_AUTH_TOKEN",
"docker.io/idconstruct/mcp-exec:v0.5.4"
],
"env": {
"MCP_EXEC_TRANSPORT": "your-value",
"MCP_EXEC_DEFAULT_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_OUTPUT_BYTES": "your-value",
"MCP_EXEC_MAX_STDIN_BYTES": "your-value",
"MCP_EXEC_AUTH_TOKEN": "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": {
"exec": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_EXEC_TRANSPORT",
"-e",
"MCP_EXEC_DEFAULT_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_TIMEOUT_S",
"-e",
"MCP_EXEC_MAX_OUTPUT_BYTES",
"-e",
"MCP_EXEC_MAX_STDIN_BYTES",
"-e",
"MCP_EXEC_AUTH_TOKEN",
"docker.io/idconstruct/mcp-exec:v0.5.4"
],
"env": {
"MCP_EXEC_TRANSPORT": "your-value",
"MCP_EXEC_DEFAULT_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_TIMEOUT_S": "your-value",
"MCP_EXEC_MAX_OUTPUT_BYTES": "your-value",
"MCP_EXEC_MAX_STDIN_BYTES": "your-value",
"MCP_EXEC_AUTH_TOKEN": "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.
MCP_EXEC_TRANSPORT envMCP_EXEC_DEFAULT_TIMEOUT_S envMCP_EXEC_MAX_TIMEOUT_S envMCP_EXEC_MAX_OUTPUT_BYTES envMCP_EXEC_MAX_STDIN_BYTES 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 6, 2026
The registry name was verified with the GitHub account inhuman, 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: MCP_EXEC_AUTH_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 (0.5.4) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker 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.
English | Русский
Public OSS MCP server (Go, MIT) exposing a single powerful tool — `exec` — that runs caller-supplied Python code in a network-isolated, locked-down sandbox and returns stdout / stderr / exit_code. It is the "code-execution mode" building block: instead of flooding an agent's context with hundreds of tool schemas, the agent writes code that orchestrates the work.
Works over three transports — stdio / HTTP / SSE — with an identical tool set everywhere (official modelcontextprotocol/go-sdk).
exec toolInput: { code: string (required), timeout_s?: int, stdin?: string } Output: { stdout, stderr, exit_code, duration_ms, truncated, timed_out }
exit_code or timed_out=true is a normal result, not a tool error. Only invalid input (empty code, oversized stdin) is a tool-call error.Per execution: no network, non-root, cap-drop=ALL, no-new-privileges, read-only rootfs, no CAP_SYS_ADMIN, ephemeral tmpdir (cleaned up), wall-clock timeout (kills the whole process-group), memory/PID/CPU limits, capped output (1 MiB → truncated). Runs are serialized within an instance; scale out with replicas. Caller data (code/stdin/output) is never persisted and never logged in full — only metadata.
execis the most powerful surface there is. When embedding it in an agent, gate it behind that
agent's tool-policy (trusted roles only).
Network note: --network none only applies to stdio. In HTTP/SSE the container needs networking to serve its port, so sandboxed code would inherit egress — deny it at the orchestrator. In k8s, a NetworkPolicy that allows ingress to the port and denies all egress:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy metadata: { name: mcp-exec-lockdown } spec: podSelector: { matchLabels: { app: mcp-exec } } policyTypes: [Ingress, Egress] ingress: [{ ports: [{ port: 8080 }] }] egress: [] # deny all egress → sandbox has no network
go build -o mcp-exec ./cmd/mcp-exec
MCP_EXEC_TRANSPORT=stdio ./mcp-exec
Docker (recommended production posture):
docker run --rm -i --network none --read-only --cap-drop ALL \
--security-opt no-new-privileges --user 65532:65532 \ --tmpfs /tmp:rw,noexec,nosuid,size=64m \ --memory 256m --pids-limit 128 --cpus 1 \ idconstruct/mcp-exec
--tmpfs /tmp is required: the rootfs is read-only, and each run needs a writable ephemeral workspace (cleaned up after).
Set MCP_EXEC_AUTH_TOKEN to require every HTTP/SSE request to carry a matching X-MCP-AUTH header (constant-time compare; 401 otherwise). Empty token disables it. Not applicable to stdio.
| Env var | Purpose | Default | ||
|---|---|---|---|---|
MCP_EXEC_TRANSPORT | stdio \ | http \ | sse | stdio |
MCP_EXEC_ADDR | listen address for http/sse | :8080 | ||
MCP_EXEC_DEFAULT_TIMEOUT_S | default wall-clock timeout | 30 | ||
MCP_EXEC_MAX_TIMEOUT_S | timeout ceiling | 300 | ||
MCP_EXEC_MAX_OUTPUT_BYTES | combined stdout+stderr cap | 1048576 | ||
MCP_EXEC_MAX_STDIN_BYTES | stdin size cap | 1048576 | ||
MCP_EXEC_PYTHON | interpreter path | python3 | ||
MCP_EXEC_AUTH_TOKEN | if set, http/sse require X-MCP-AUTH header (constant-time); empty = off | |
bash / multi-language, network from the sandbox, proxying other MCP servers into the sandbox.
MIT.