servers / mcp-server-spec-driven-development
mcp-server-spec-driven-development
communitystdiolocalunknownhealthy
Spec-Driven Development MCP Server, not just Vibe Coding
01Tools · 0
Tools require a live
tools/list handshake. For local/stdio servers that runs in a sandbox (gated off until configured); remote servers are probed directly.02Install & source
npx -y mcp-server-spec-driven-development@latest
npx- repohttps://github.com/formulahendry/mcp-server-spec-driven-development
- homepagehttps://www.npmjs.com/package/mcp-server-spec-driven-development
- licenseMIT
- adoption435 stars · 39 forks
05Provenance & freshness
sourcesGitHub repo search [p4]
last_checked2026-08-05 01:50Z
next_check2026-09-04 01:49Z
cadenceevery 720h
verifiedtools_list:failed handshake:passed metadata:passed tools_list:failed handshake:passed metadata:passed tools_list:failed handshake:passed metadata:passed metadata:passed
index_statusindex — 7 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README.
[](https://mcpexplorer.com/servers/mcp-server-spec-driven-development)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →