Spec 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 |
|---|---|
| generate-codebase-analysisA | Analyzes codebase and generates three foundational analysis documents: product.md, tech.md, and structure.md in .spec/steering/ directory. These documents provide comprehensive analysis of the product features, technology stack, and project structure. Checks if files already exist and skips generation unless force_regenerate is true. |
| generate-tasksA | Generate tasks.md (implementation plan & task breakdown) from your request and codebase. Writes |
| task-orchestratorA | Use this to implement/execute existing tasks from tasks.md that have already been defined. This tool assumes tasks already exist and focuses on coordinating their implementation. DO NOT use this for generating new plans or tasks - only for executing tasks that have already been created. |
| task-executorB | Executes a specific task from tasks.md by providing detailed implementation guidance, requirements, acceptance criteria, and code patterns. This tool focuses on implementing one task thoroughly. |
| task-checkerC | Prompt-only verification: instructs the agent to verify acceptance criteria checkboxes for a task with quoted evidence. Returns a PASS/FAIL decision rule to apply. |
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 5 tools
The tools have overlapping purposes that could cause confusion, particularly between task-executor and task-orchestrator which both handle task implementation with unclear boundaries. However, descriptions help clarify that task-orchestrator is for coordinating multiple existing tasks while task-executor focuses on single-task implementation, and the other tools have more distinct roles.
Tool names follow a consistent verb_noun pattern (e.g., generate-codebase-analysis, generate-tasks, task-checker) with clear, descriptive naming. The only minor deviation is that 'task-checker' and 'task-executor' use hyphenated compound nouns rather than separate verb_noun pairs, but the pattern remains readable and predictable throughout.
With 5 tools, the count is well-scoped for the server's purpose of specification and task management. Each tool earns its place by covering distinct phases: analysis generation, task planning, verification, and implementation, making the set neither too thin nor overloaded for the domain.
The tool surface covers the core workflow from codebase analysis to task execution with minor gaps. It includes analysis generation, task planning, verification, and implementation tools, but lacks explicit tools for updating or deleting generated documents or tasks, which agents might need to work around by regenerating files.