Spec-driven Development MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kevinlin/spec-driven-dev-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server