servers / mcp-server-spec-driven-development

mcp-server-spec-driven-development

communitystdiolocalhealthy

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
Local · npx
npx -y mcp-server-spec-driven-development@latest

05Provenance & freshness
sourcesGitHub repo search [p4]
last_checked2026-11-03 02:10Z
next_check2026-12-03 02:10Z
cadenceevery 720h
verifiedmetadata:passed metadata:passed metadata:passed tools_list:failed handshake:passed metadata:passed tools_list:failed handshake:passed metadata:passed tools_list:failed
index_statusindex — 7 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. mcp-server-spec-driven-development MCP — as seen on mcpexplorer.com

[![mcp-server-spec-driven-development MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/mcp-server-spec-driven-development.svg)](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 →