# speckitacceptance-mcp

A paid remote MCP server that gates spec-driven development: it checks diffs against requirements and issues structured acceptance receipts.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: clauxel
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/clauxel/spec-kit-acceptance-gate-mcp
- Updated: 2026-05-20
- HTML: https://affpapa.org/en/nevibecode/mcp/speckitacceptance-mcp

## What it does

The server speaks Streamable HTTP and answers JSON-RPC calls. Five tools cover the acceptance path: `check_spec_acceptance` reviews a spec, `map_diff_to_requirements` ties code changes to requirement items, `verify_acceptance_evidence` confirms the evidence, `issue_acceptance_receipt` produces a structured receipt, and `export_acceptance_audit` dumps the audit trail.

Access is paid and hosted. Production calls need a bearer token issued from the product website after you pick a plan. Unauthenticated requests to `/mcp` fail: a plain browser visit gets a JSON error instead of internal details. The token goes in the `Authorization: Bearer <token>` header.

The repository holds public documentation and directory links only — production source is not there. If you want an offline acceptance tool, this is the wrong pick, because every call depends on the remote endpoint `https://speckitacceptance.clauxel.com/mcp`.

## Requirements
- Remote server: `https://speckitacceptance.clauxel.com/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http speckitacceptance-mcp https://speckitacceptance.clauxel.com/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add speckitacceptance-mcp --url https://speckitacceptance.clauxel.com/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "speckitacceptance-mcp": {
            "url": "https://speckitacceptance.clauxel.com/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "speckitacceptance-mcp": {
            "type": "http",
            "url": "https://speckitacceptance.clauxel.com/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http speckitacceptance-mcp https://speckitacceptance.clauxel.com/mcp
```

## When to use it
- check a diff against spec requirements before merging
- produce a structured acceptance receipt for a reviewer
- export the acceptance audit trail
- confirm evidence that requirements were met
- see whether an implementation actually closes the spec

## Example prompts
- Run the spec acceptance check on my current branch through speckitacceptance-mcp
- Map the diff to the requirements and list what is still open
- Export the acceptance audit from the last run

## Similar
- [scaffolder](https://affpapa.org/en/nevibecode/agents/scaffolder.md) — subagent · ★ 44770
- [story-done](https://affpapa.org/en/nevibecode/skills/story-done.md) — skill · 413 installs
- [indexion-sdd](https://affpapa.org/en/nevibecode/skills/indexion-sdd.md) — skill · 5000 installs
- [backprop](https://affpapa.org/en/nevibecode/skills/backprop.md) — skill · 2600 installs
- [check](https://affpapa.org/en/nevibecode/skills/juliusbrussee-check.md) — skill · 2700 installs
- [tlc-spec-driven](https://affpapa.org/en/nevibecode/skills/tlc-spec-driven.md) — skill · 1200 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md