Spec-driven Development MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spec_coding_workflow_startB | Start the specs workflow and begin the goal collection phase |
| spec_coding_goal_confirmedB | Confirm the completion of the feature goal, set the feature_name, and proceed to the requirements collection phase |
| spec_coding_requirements_startC | Start the requirements collection phase and provide guidance for requirements gathering |
| spec_coding_requirements_confirmedC | Confirm the completion of requirements collection and proceed to the design phase |
| spec_coding_design_startC | Start the design documentation phase and provide guidance for creating design documents |
| spec_coding_design_confirmedC | Confirm the completion of the design document and proceed to the task planning phase |
| spec_coding_tasks_startC | Start the task planning phase and provide guidance for creating the task list |
| spec_coding_tasks_confirmedC | Confirm the completion of task planning and proceed to the execution phase |
| spec_coding_execute_startC | Start the task execution phase and provide guidance for task execution |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose corresponding to a specific phase in the spec-driven development workflow. The naming convention with phase names (goal, requirements, design, tasks, execute) and action suffixes (_start, _confirmed) eliminates any ambiguity about which tool to use for which workflow step.
All tools follow an identical pattern: 'spec_coding_' + [phase_name] + '_' + [action]. This consistent snake_case structure with predictable verb endings (_start, _confirmed) creates excellent predictability and readability across the entire tool set.
With 9 tools, this server perfectly covers the complete spec-driven development lifecycle from workflow initiation through execution. Each tool represents a distinct phase transition, making the count well-scoped and appropriate for managing this structured development process.
The tool set provides complete coverage of the spec-driven development workflow, including all phase transitions from workflow start through execution. There are no gaps - every phase has both a start and confirmed tool, creating a complete, linear progression without dead ends for agents to follow.