Speckitacceptance MCP

What speckitacceptance-mcp MCP server does

The speckitacceptance-mcp MCP server supports acceptance decisions in spec-driven development. It is delivered as a paid hosted service rather than as source code in this repository. The service is intended for workflows where a change must be checked against requirements, supported with evidence, and recorded for later review.

Its output model centers on structured receipts, audit logs, and reviewer-ready evidence. The repository does not document the internal implementation or define the detailed request and response schemas for each tool, so clients should consult the service’s server card or product documentation before building an integration around specific fields.

How it works

The hosted MCP endpoint is available at https://speckitacceptance.clauxel.com/mcp. Clients connect over Streamable HTTP and send MCP JSON-RPC requests. Production requests must include a bearer token in the authorization header:

Authorization: Bearer <token>

The access flow starts on the product website. A user selects a plan, creates or requests an API token, configures an MCP client that supports remote Streamable HTTP servers, and then sends authenticated requests to the endpoint. Unauthenticated browser requests receive a JSON error rather than internal service details.

Tools and capabilities

The speckitacceptance-mcp MCP server exposes five tools:

• check_spec_acceptance checks acceptance against a specification-driven workflow.
• map_diff_to_requirements relates a change or diff to stated requirements.
• verify_acceptance_evidence verifies evidence supplied for an acceptance decision.
• issue_acceptance_receipt creates a structured acceptance receipt.
• export_acceptance_audit exports acceptance-related audit information.

Together, these tools cover the documented acceptance-gate flow: evaluate a specification, connect implementation changes to requirements, validate supporting evidence, produce a receipt, and export an audit record. The README lists the tools but does not provide their parameter definitions, validation rules, or response formats.

Setup and configuration

This service requires a paid plan and a production bearer token issued through the product website. Configure the remote endpoint in an MCP client with Streamable HTTP support, then provide the token as an authorization credential. No named environment variable is specified by the repository, and the README does not describe a local installation or self-hosted mode.

The repository functions as public documentation and a directory-submission reference. It does not include the private production source code. Useful service references include the server card at https://speckitacceptance.clauxel.com/server-card.json and the product page at https://speckitacceptance.clauxel.com/.

Limitations and notes

The speckitacceptance-mcp MCP server is remote and authenticated, so it is not suitable for an offline or source-available deployment based on the repository alone. Access also depends on the service’s paid plan and token-issuance process. Before implementing automation, confirm the supported request schemas and client behavior from the server card or provider documentation because the supplied README does not specify tool arguments, return values, rate limits, or retention details.