Sanity vs Speckitacceptance MCP
A side-by-side look at the Sanity and Speckitacceptance MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sanity for developer tools work as a local process; choose Speckitacceptance MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Sanity when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
query_documents, create_documents, patch_documents.
Choose Speckitacceptance MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_spec_acceptance, map_diff_to_requirements, verify_acceptance_evidence.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 64/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 192 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | 5 |
| Full listing | View Sanity | View Speckitacceptance MCP |
Tools & capabilities
Sanity tools 8
query_documentsrun GROQ queries directlycreate_documentscreate draft documents from structured content, or version documents when a release ID is providedpatch_documentssurgical edits to existing documents; published documents are edited by creating or updating draftsdeploy_studiodeploy a hosted Studio bound to an MCP-managed schemacreate_versioncreate version documents for releaseswhoamiverify the authenticated Sanity userget_project_studioslist Studio applications linked to a projectgive_feedbackreport MCP tool errors, missing capabilities, confusing output, or documentation issues
Speckitacceptance MCP tools 5
check_spec_acceptancemap_diff_to_requirementsverify_acceptance_evidenceissue_acceptance_receiptexport_acceptance_audit
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Sanity
{
"mcpServers": {
"sanity": {
"command": "npx",
"args": [
"-y",
"sanity@latest"
]
}
}
}
Speckitacceptance MCP
{
"mcpServers": {
"speckitacceptance-mcp": {
"url": "https://speckitacceptance.clauxel.com/mcp"
}
}
}
Frequently asked questions
Sanity is categorized under Developer Tools and uses a local stdio subprocess. Speckitacceptance MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Sanity for developer tools work and Speckitacceptance MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Sanity has no declared pricing — check the project's own site. Auth: oauth 2.0. Speckitacceptance MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sanity and speckitacceptance-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sanity has a quality signal of 64/100 (Good) with 1 views, 0 installs and 192 GitHub stars. Speckitacceptance MCP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.