OpenSpec 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openspec_initC | Initialize OpenSpec in your project |
| openspec_updateC | Update OpenSpec instruction files |
| openspec_listC | List items (changes or specs). Returns a JSON array when --json is used. |
| openspec_showB | Show a change or spec. Use type to specify if it is ambiguous. |
| openspec_validateC | Validate a change proposal or spec |
| openspec_archiveC | Archive a completed change and update main specs |
| openspec_new_changeC | Create a new change directory |
| openspec_statusC | Display artifact completion status for a change |
| openspec_instructionsC | Output enriched instructions for an artifact or apply |
| openspec_read_fileA | Read any OpenSpec artifact directly. Much faster than show — use this when you need file contents. |
| openspec_refresh_cacheA | Force refresh the cached directory listing. Use if you suspect changes were made outside OpenSpec tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| openspec_kickoff | Initialize an AI coding session using Fission-AI OpenSpec best practices. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes, but openspec_show and openspec_read_file overlap in reading file content, though the description notes read_file is faster for raw contents. Other tools like list/status are distinct enough.
All tools share the openspec_ prefix and use snake_case. However, verbs (init, list, show) are mixed with nouns (status, instructions) and phrases (new_change). The pattern is consistent in terms of prefix but not strictly verb_noun.
11 tools is well within the ideal range for a domain-specific server. Each tool covers a distinct aspect of OpenSpec project management, from initialization to archiving.
The tool set covers the core workflow: initialize, create, view, validate, status, and archive changes. Missing operations like delete or edit change are possible but not obviously required for OpenSpec's workflow, and the surface feels comprehensive.