Developer · Remote MCP server
SpecPilot
Generate and validate a.specs/ bundle for your repo, then hand it to your AI coding agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.specpilot/specpilot- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-13
- Updated
- 2026-09-13
- Publisher
- dev.specpilot
- Namespace
- Namespace verified by the MCP Registry via the domain specpilot.dev · how
- Website
- specpilot.dev/mcp-setup
- Repository
- github.com/girishr/SpecPilot
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://init.specpilot.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- specpilot 1.0.0 · protocol 2025-06-18
- Tools discovered
- 2:
specpilot_next_questions,specpilot_generate_specs - Checked on
- 2026-10-05
How to connect SpecPilot
SpecPilot is a remote MCP server: there is nothing to install. Its endpoint is https://init.specpilot.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Spec Score MCPScore your specs before feeding them to an LLM. MCP server with radar chart visualization. | Local · stdio |
| Speckitacceptance MCPPaid remote MCP for spec driven development acceptance gate MCP, structured receipts, audit logs, an. | Remote · HTTPLive check: ✗ no handshake |
| SpecLeftPython intent tracing MCP: map specs to pytest tests, monitor implementation progress, offline-only. | Local · stdio |
| specmateBSV coding knowledge engine for AI agents - pre-compile traps and post-compile diagnosis. | Local · stdio |
| Specshield MCP ServerThe API-change deploy gate for AI coding agents. Read-only breaking-change detection. | Local · stdio |
| SpectraGenerates unit tests for Python code with coverage before/after reports and concrete edge cases. | Remote · HTTPLive check: sign-in required |
| speedreadToken-efficient code reading for coding agents: symbol-aware, budgeted, diff-aware reads. | Local · stdio |
| spendtronFinds the GitHub Actions workflow eating your CI bill and suggests fix diffs, verified against runs. | Remote · HTTPLive check: ✓ handshake |