MCP reference
The spec-editor MCP server gives external agents (Claude Code, Cursor and others that speak MCP) exactly the elements they need. It has 72 tools in the open core and 44 more with spec-editor Pro. The server runs over stdio, HTTP or a Unix socket; start it with spec-editor mcp.
The lists on these pages are the tools of a server that opens a project for writing. A server started with --read-only hides the tools that change the project. Tools marked Pro exist only when the Pro plugin is installed.
Groups
| Group | Tools | Pro tools | What it covers |
|---|---|---|---|
| Spec | 22 | 1 | Read, search and change the elements of the requirements model. |
| Journal | 8 | 0 | Query the journal of runs, agents and elements, the delivery lanes and the duty summary. |
| Runtime | 6 | 0 | Operation events of the running system and the trace level of an element. |
| Diff | 4 | 1 | Versions of elements and code, and the change sets between them. |
| Export | 9 | 0 | Export the specification, generate diagrams, read git history and source documents. |
| Project and system | 8 | 0 | Discover projects, read their methodology and state, and ask the server about teams, agents and capabilities. |
| Agent | 7 | 1 | Questions to the user and the context of an agent. |
| Skills | 2 | 0 | The skills catalog: metadata and full text. |
| Visual | 2 | 0 | Saved layouts of the visual views. |
| Code | 8 | 7 | Search and check the code, and annotate it with implements markers. |
| Channels | 4 | 0 | External channels: trackers and logs. |
| Cycle | 14 | 13 | Incident intake, bug handling, delegation and the steps of the delivery cycle. |
| Gates | 6 | 6 | Risk classes and approval gates. |
| Breakpoints | 12 | 12 | Feedback captured on a screen of the running product and bound to requirements. |
| Cost and usage | 4 | 3 | Cost of work per task and source, account pool records and the usage of tools per role. |