Server facts
specs-workflow-mcp
Project
- Author
- kingkongshot
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 127
- Last commit
- Data as of
Tags
- kiro
- spec
- workflow
Overview
Software planning in specs-workflow-mcp centers on linked requirements, design, and task documents. Developers describe a feature or project, and the AI builds documentation covering user stories, functional needs, architecture, APIs, data models, and numbered implementation steps. The workflow asks for approval between stages, giving users a chance to review the proposed direction before moving forward. Its specs-workflow tool supports initialization, status checks, stage skipping, confirmation, and completion of individual tasks or batches.
For ongoing work, progress checks let the assistant identify the project's current state and resume from that point. Completing a task returns the next pending task's content, connecting the documented plan with subsequent implementation work. Documentation can live in a chosen directory, with either a shared project structure or separate folders for modules such as authentication and payments. Progress is tracked in a confirmation file alongside the documents. The integration uses stdio and includes setup examples for Claude Code, Claude Desktop, Cursor, Cline, Windsurf, VS Code, and Zed.
specs-workflow-mcp setup notes
- specs-workflow-mcp records stdio only; confirm a network transport upstream before planning remote access.
- specs-workflow-mcp has no recorded license; confirm reuse terms in its repository.