OpenSpec MCP
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openspec_get_instructionsA | Get OpenSpec usage instructions from AGENTS.md |
| openspec_get_project_contextB | Get project context from project.md |
| openspec_list_changesC | List all OpenSpec change proposals |
| openspec_list_specsB | List all OpenSpec specifications |
| openspec_show_changeB | Show details of a specific change proposal |
| openspec_show_specB | Show details of a specific specification |
| openspec_validate_changeC | Validate a change proposal |
| openspec_validate_specC | Validate a specification |
| openspec_validate_allC | Validate all changes and/or specs |
| openspec_archive_changeA | Archive a completed change proposal. Automatically syncs revisions to design.md before archiving. |
| openspec_get_tasksB | Get tasks and progress for a change |
| openspec_update_taskB | Update task status |
| openspec_get_progress_summaryA | Get progress summary for all changes |
| openspec_batch_update_tasksB | Batch update multiple task statuses in a change |
| openspec_get_approval_statusC | Get approval status for a change |
| openspec_request_approvalC | Request approval for a change |
| openspec_approve_changeC | Approve a change |
| openspec_reject_changeC | Reject a change |
| openspec_list_pending_approvalsA | List all changes pending approval |
| openspec_add_reviewC | Add a review comment to a change or spec |
| openspec_list_reviewsC | List review comments for a change or spec |
| openspec_reply_reviewC | Reply to a review comment |
| openspec_resolve_reviewC | Mark a review as resolved or won't fix |
| openspec_get_review_summaryB | Get review summary for a change (all files) |
| openspec_list_templatesA | List all available change templates |
| openspec_create_changeB | Create a new change from a template |
| openspec_preview_templateB | Preview the content of a template |
| openspec_setup_hooksB | Install or uninstall OpenSpec Git hooks |
| openspec_save_proposalC | Save a generated proposal and tasks to a new change |
| openspec_generate_proposalA | Generate a proposal from requirement description (returns template for AI to complete) |
| openspec_list_cross_service_docsA | List cross-service documents for a change proposal. Returns documents defined in proposal.md frontmatter crossService config. |
| openspec_read_cross_service_docA | Read a specific cross-service document content. Use openspec_list_cross_service_docs first to see available documents. |
| openspec_critique_proposalA | 评审 proposal 或 design 文档，识别潜在问题（完整性、可行性、安全、边界条件、清晰度） |
| openspec_get_critique_resultC | 获取变更的评审结果（最新或历史记录） |
| openspec_analyze_contextC | 分析项目上下文（技术栈、目录结构、代码模式） |
| openspec_ai_analyze_contextC | 使用 AI 深度分析项目上下文并给出 project.md 更新建议。 利用 MCP Client 的 AI 能力进行分析。 |
| openspec_record_revisionA | Record a design revision when fixing bugs or adjusting design that deviates from the original proposal/design. Call this when your changes affect the documented design. |
| openspec_update_revisionC | Update an existing revision, usually to add metadata or correct information. |
| openspec_list_revisionsB | List all recorded design revisions for a change |
| openspec_sync_revisionsC | Sync recorded revisions to design.md or proposal.md before archiving |
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 40 tools
Most tools have distinct purposes (e.g., create vs. list vs. approve), but a few pairs like openspec_analyze_context and openspec_ai_analyze_context, or openspec_get_critique_result and openspec_get_review_summary, could cause confusion due to overlapping scope.
All tools follow a consistent 'openspec_verb_noun' pattern with underscores, and verbs are descriptive (e.g., add, create, list, validate). No mixing of casing or conventions.
With 40 tools, the count far exceeds the typical well-scoped range of 3-15. While the domain is broad, many tools are specialized (e.g., openspec_setup_hooks) and would benefit from consolidation.
The tool set covers most lifecycle operations for changes, specs, reviews, tasks, and proposals. However, missing a direct delete/edit for changes/specs and lack of spec creation tools leave minor gaps.