Spec Kit 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 |
|---|---|
| speckit_constitutionB | Establish project principles using spec-kit |
| speckit_specifyC | Describe what to build |
| speckit_planC | Create a technical plan |
| speckit_tasksD | Generate task list |
| speckit_implementD | Execute implementation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| speckit.constitution | Establish project principles using spec-kit |
| speckit.specify | Describe what to build |
| speckit.plan | Create a technical plan |
| speckit.tasks | Generate task list |
| speckit.implement | Execute implementation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose in the spec-kit workflow: constitution (principles), plan (technical plan), specify (description), tasks (task list), and implement (execution). There is no overlap or ambiguity between these stages, making tool selection straightforward for an agent.
All tool names follow a consistent 'speckit_' prefix with a descriptive action suffix (e.g., constitution, implement, plan, specify, tasks). This uniform pattern enhances readability and predictability across the toolset.
With 5 tools, the server is well-scoped for its purpose of project specification and implementation. Each tool represents a distinct phase in the workflow, and the count is neither too sparse nor excessive for the domain.
The toolset provides complete coverage of the spec-kit lifecycle, from establishing principles (constitution) and planning to specifying, task generation, and implementation. There are no obvious gaps, and the tools logically progress through the project development stages.