@precode/mcp

Public MCP server on npm that turns a spec into a self-correcting, verified build. Works with any spec format (SPEC.md, .specify, .spec-workflow) and is optimized for a PreCode .precode/ documentation package. Free to use, runs locally on your agent and your tokens — no PreCode account required.

Install: @precode/mcp on npm. Docs: useprecode.vercel.app/mcp.

It fixes the loop/goal failure other spec MCPs ship with:

• Goal re-anchoring — the agent re-reads the goal every phase, so long builds don't drift.
• Hard definition-of-done — when you declare checks in .precode/checks.json, the MCP runs them itself and the verdict comes from the real exit codes. A fabricated "it passed" cannot move a task to done.
• Closed verify → fix → re-verify — gaps come back with fixes and the loop will not advance past them.
• Honest escapes — a check that genuinely can't pass here (needs a secret, a deploy, a paid service) is precode.defer_task'd with a reason and surfaced in TODO_FOR_YOU.md, never silently skipped.

At the end it writes an IMPLEMENTATION.md (what was built) and a TODO_FOR_YOU.md (what you still need to do — secrets, env, deploy).

Install

Recommended: install globally, then point your MCP host at the precode-mcp binary:

npm i -g @precode/mcp

{
  "mcpServers": {
    "precode": {
      "command": "precode-mcp",
      "env": { "PRECODE_TELEMETRY_DISABLED": "1" }
    }
  }
}

npx fallback (use quiet flags so install logs do not pollute stdio):

{
  "mcpServers": {
    "precode": {
      "command": "npx",
      "args": ["-y", "--silent", "@precode/mcp"],
      "env": {
        "PRECODE_TELEMETRY_DISABLED": "1",
        "NPM_CONFIG_LOGLEVEL": "silent",
        "npm_config_update_notifier": "false"
      }
    }
  }
}

Full per-host copy-paste configs: useprecode.vercel.app/mcp.

Cursor / Claude Desktop / Windsurf / Antigravity — install globally first (npm i -g @precode/mcp), then:

{
  "mcpServers": {
    "precode": {
      "command": "precode-mcp",
      "env": { "PRECODE_TELEMETRY_DISABLED": "1" }
    }
  }
}

Claude Code:

npm i -g @precode/mcp && claude mcp add --env PRECODE_TELEMETRY_DISABLED=1 --transport stdio --scope project precode -- precode-mcp

Codex CLI:

npm i -g @precode/mcp && codex mcp add precode -- precode-mcp

VS Code — note "servers" wrapper and optional "cwd": "${workspaceFolder}":

{
  "servers": {
    "precode": {
      "type": "stdio",
      "command": "precode-mcp",
      "cwd": "${workspaceFolder}",
      "env": { "PRECODE_TELEMETRY_DISABLED": "1" }
    }
  }
}

Do not use bare npx -y @precode/mcp without --silent and npm log suppression — install logs on stdout corrupt the JSON-RPC channel. Use the npx fallback JSON at the top of this file if global install is impossible.

The server reads .precode/ from the directory the host runs it in (PRECODE_ROOT overrides). Local stdio only — the build loop needs your filesystem.

Telemetry

Telemetry is off unless PRECODE_TELEMETRY_URL is set. When enabled, the server sends privacy-safe beta events such as mcp_next_task, mcp_verify_pass, and mcp_finalize; it hashes the local root path and never sends spec contents, file contents, secrets, or task text. Set PRECODE_TELEMETRY_DISABLED=1 to force-disable it.

Use

1. Drop a PreCode export (or run precode.adopt_spec on your own SPEC.md).
2. Run the precode_build prompt, or just tell your agent: "build this with the precode loop."

Local Verification

npm run test:stdio

The smoke test launches the built MCP server over stdio, verifies the tool list, runs a real executable check, confirms a failing check (and a fabricated passing report) keep the task open, confirms the task closes only once the real check passes, reads precode://docs, and writes the final TODO_FOR_YOU.md. npm test runs the full edge-case suite (test/run.mjs + test/edge.mjs). See EDGE_CASES.md for the verified matrix and known limitations.

Tools

Checks — the executable done-gate

Declare checks in .precode/checks.json. Each auto check is run by the MCP from the project root on every precode.verify; the task closes only when its real exit code is 0.

{
  "checks": [
    { "id": "typecheck", "name": "Type-check", "kind": "auto", "cmd": "npm run typecheck" },
    { "id": "build", "name": "Build", "kind": "auto", "cmd": "npm run build" },
    { "id": "test", "name": "Tests", "kind": "auto", "cmd": "npm test", "expect": "/\\d+ passing/" },
    { "id": "deploy-task-3", "name": "Smoke route /health", "kind": "auto", "cmd": "curl -fsS localhost:3000/health", "taskIndex": 3 },
    { "id": "secrets", "name": "Prod secrets set in real accounts", "kind": "manual" }
  ]
}

• kind: "auto" — executed; pass = exit 0 (and expect substring//regex/ matches combined stdout+stderr if set). Optional timeoutMs (default 120s). Output usually ends in a trailing newline, so prefer a substring or "/^alpha\n?$/" over a hard-anchored "/^alpha$/".
• kind: "manual" — never auto-passed; surfaced as a human gate in TODO_FOR_YOU.md (a manual-only task closes with its gate routed to you).
• taskIndex (alias task) — bind a check to one task; it then runs only at that task's verify. Setting it implies scope: "task". Omit to run on every task's verify.
• A task never closes on a self-reported pass. Reported checkResults are advisory only. A check declared with an empty cmd is treated as unconfigured and HOLDs the task — wire a real command, mark it manual, or precode.defer_task.
• adopt_spec infers real commands from your project (package.json scripts, Cargo.toml, go.mod) so a fresh spec is verifiable out of the box. Only when nothing is detected does it write empty placeholders that HOLD until you fill them. Failure advice references the actual command that ran, and defer_task is refused if the task's checks actually pass (so it can't be used to dodge verifiable work). Global manual gates are listed once in TODO_FOR_YOU.md, not repeated per task.

Security: the runner only executes commands you put in your own repo's checks.json — the same trust level as the agent already running your build. Commands run with a timeout and captured output. Because checks.json lives in your repo, gate tampering shows up in your diff.

Multi-agent / concurrent verify

precode.verify runs the checks lock-free and holds .precode/.lock only for the brief tasks.md mutation. So two agents can verify different ready tasks at the same time — their checks execute in parallel and only the tiny state write serializes.

• Pass taskIndex to verify a specific dependency-ready task (e.g. precode.verify { "taskIndex": 4 }). Omit it to verify the next ready task. This is how parallel agents target distinct tasks.
• If two verifies hit the same task, exactly one closes it; the other gets a graceful "Task #N was already verified by a concurrent run" (no clobber, no double-close).
• Locks are token-owned — only the holder releases; a wrong token cannot drop someone else's lock. The mutation lock briefly blocks-and-retries rather than failing fast.
• Stale locks (e.g. crashed agent) are stolen after 5 minutes via compare-and-unlink. Override with PRECODE_LOCK_STALE_MS (milliseconds) — e.g. 10000 for 10s in local dev.
• Failed verify records the failure under the lock and releases it so another agent can retry the same open task.

parallelGroup: controls scheduling — any member may be returned by precode.next_task, and parallel agents verify them concurrently by passing each member's taskIndex.

See EDGE_CASES.md for the full stress-test matrix.

Resources

Release

Tagged releases publish to npm via GitHub Actions. See RELEASE.md.