mcp-server-spec-driven-development and interactive-mcp
About mcp-server-spec-driven-development
formulahendry/mcp-server-spec-driven-development
Spec-Driven Development MCP Server, not just Vibe Coding
Implements a three-stage MCP workflow that chains requirements generation (EARS format) → design documents → code output, with each stage reading structured specs from the previous phase. Integrates directly into VS Code, Cursor, and Claude Code via npx installation, communicating through the Model Context Protocol to enable AI-assisted development from specification to implementation.
About interactive-mcp
ttommyth/interactive-mcp
Vibe coding should have human in the loop! interactive-mcp: Local, cross-platform MCP server for interact with your AI Agent
Implements five MCP tools that enable bidirectional communication: `request_user_input` with optional predefined choices, OS notifications, and persistent command-line chat sessions for multi-turn interactions. Runs as a local Node.js/TypeScript server communicating via stdio with MCP clients (Claude Desktop, Cursor, VS Code), requiring direct OS access for displaying prompts and notifications. Supports configurable timeouts and granular tool disabling through command-line flags.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work