Search / dev.specpilot/specpilot
protogridR0· no sign-inGenerate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
v1.0.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"specpilot": {
"type": "http",
"url": "https://init.specpilot.dev/mcp"
}
}
}claude mcp add --transport http specpilot https://init.specpilot.dev/mcp[mcp_servers.specpilot]
url = "https://init.specpilot.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"specpilot": {
"type": "remote",
"url": "https://init.specpilot.dev/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"specpilot": {
"type": "http",
"url": "https://init.specpilot.dev/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=specpilot&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vaW5pdC5zcGVjcGlsb3QuZGV2L21jcCJ9"
}{
"servers": {
"specpilot": {
"type": "http",
"url": "https://init.specpilot.dev/mcp"
}
}
}{
"mcpServers": {
"specpilot": {
"httpUrl": "https://init.specpilot.dev/mcp"
}
}
}extensions:
"specpilot":
enabled: true
name: "specpilot"
type: streamable_http
uri: "https://init.specpilot.dev/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: specpilot_next_questions (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); specpilot_generate_specs (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 3,565 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-96% ~updated-37d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://init.specpilot.dev/mcp streamable-http | none | yes | 96% | 441 ms | 2025-11-25 | 2026-10-19 |
specpilot_generate_specs | Generates the complete SpecPilot .specs/ file set plus the matching IDE rules and slash-command files from a full answer set - identical to what the SpecPilot web chat produces for the same answers. Requires projectName and projectDescription. Returns the files to write and the steps to follow after writing them. |
specpilot_next_questions | Returns the still-unanswered SpecPilot onboarding questions of the next incomplete step, gated by the answers supplied so far - questions that do not apply to this kind of project are omitted, and options are filtered, badged or flagged the same way the SpecPilot web chat would. Stateless: send every answer collected so far on each call. Procedure: (1) Decide whether the repository already has real source code and set `isNewBuild` accordingly - it changes which onboarding analysis is generated at the end. (2) Infer what the repo already answers rather than asking: `platforms` from the dependency manifests and layout, `languageOverride`, `ideAgent` (you are the IDE - claudecode, cursor, copilot, codex, windsurf), `handle` from git config or the origin remote, `projectName` from the package manifest or folder name, and `projectDescription` from the README only if it plainly says what the project is. (3) Call this tool with what you have; answer what the repo makes obvious and ask the developer the rest, a whole step per message. Send an empty value for an optional question the developer declines, or it will be asked again; send `todoSentinel` verbatim when they do not know yet. For `projectDescription`, sending one of the returned chip labels exactly is what infers `projectCategory` and gates every later question - free prose infers nothing. Confirm any pre-seeded value rather than accepting it silently. (4) Loop until `done` is true, then call specpilot_generate_specs and follow its `nextSteps` for where each file goes. |
Schemas: list_tools.
{
"name": "dev.specpilot/specpilot",
"icons": [
{
"src": "https://specpilot.dev/images/SpecPilot.svg",
"sizes": [
"any"
],
"mimeType": "image/svg+xml"
}
],
"title": "SpecPilot",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://init.specpilot.dev/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/girishr/SpecPilot",
"source": "github"
},
"websiteUrl": "https://specpilot.dev/mcp-setup",
"description": "Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent"
}