speckitmcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| speckit_initA | Initialize a new spec-kit project. Creates .specify/ directory with templates, constitution, and agent command files. Automatically confirms if the directory is non-empty. |
| speckit_checkA | Check that spec-kit and all required tools are installed. Returns version and system information. |
| speckit_versionA | Get version information for both the MCP server and the spec-kit CLI. |
| speckit_statusA | Get the status of a spec-kit project. Shows which specs, plans, tasks, checklists, research, data-model, quickstart, and contracts exist. |
| speckit_constitutionA | Read, create, or update the project constitution. The constitution defines core principles, technology choices, quality standards, and governance rules for the project. |
| speckit_specifyA | Create or update a feature specification. Creates specs/{feature}/spec.md with requirements, user stories, and acceptance criteria. |
| speckit_planA | Create or update a technical implementation plan. Creates specs/{feature}/plan.md with architecture, tech stack, and implementation approach. Also supports writing research and design artifacts. |
| speckit_tasksB | Create or update a task breakdown. Creates specs/{feature}/tasks.md with phased, actionable tasks with dependencies and parallel opportunities. |
| speckit_implementB | Track implementation progress for a feature. Read current tasks and related docs, mark tasks complete (with optional checklist gate), or add implementation notes. |
| speckit_clarifyA | Manage clarification questions for a feature. Scan spec.md for ambiguities across 9 taxonomy categories and return up to 5 prioritized questions (scan), or write an answer inline in spec.md (answer). Does not write clarifications.md. |
| speckit_analyzeA | Analyze cross-artifact consistency for a feature across 6 passes: Duplication, Ambiguity, Underspecification, Constitution Alignment, Coverage Gaps, and Inconsistency. Strictly read-only — never writes files. |
| speckit_checklistA | Create a requirement quality checklist for a feature. Generates checklists that assess spec quality (completeness, clarity, coverage, consistency) — not implementation status. Saved to specs/{feature}/checklists/{name}.md. |
| speckit_tasks_to_issuesA | Convert spec-kit tasks to GitHub issues. Reads tasks.md and creates corresponding GitHub issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| sdd_workflow | Complete Spec-Driven Development workflow guide. Walks through all phases: constitution, specify, clarify, plan, tasks, checklist, analyze, implement, tasks_to_issues. |
| sdd_constitution | Guide for creating a project constitution. Establishes principles, tech choices, and governance. |
| sdd_specify | Guide for writing a feature specification with user stories, acceptance criteria, and requirements. |
| sdd_clarify | Guide for identifying ambiguities in a specification using scan/answer actions. |
| sdd_plan | Guide for creating a technical implementation plan with research phase, data model, contracts, quickstart, and architecture. |
| sdd_tasks | Guide for breaking down a plan into phased, actionable tasks with dependencies and parallel opportunities. |
| sdd_implement | Guide for executing tasks systematically, tracking progress, and marking tasks complete. Includes checklist gate and force-bypass support. |
| sdd_analyze | Guide for validating cross-artifact consistency between spec, plan, and tasks. |
| sdd_checklist | Guide for generating requirement quality checklists stored in checklists/ subdirectory. Validates spec completeness, not implementation. |
| sdd_taskstoissues | Guide for converting a tasks.md file into GitHub issues. Supports dry_run mode (default true) and custom labels. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/jthom233/speckitmcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server