SpecPlanner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECPLANNER_DATA_DIR | No | Custom deployment data directory for SpecPlanner storage. The MCP server supports this environment variable; the native worker normally uses the default location (~/.local/share/specplanner/). | ~/.local/share/specplanner/ |
| SPECPLANNER_WORKSPACE | No | Optional legacy default workspace path. Every MCP call takes an explicit workspacePath; omission uses only this optional legacy default. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_plannerA | Open SpecPlanner for the current Codex project. Pass its absolute project directory as workspacePath using the current chat context. Do not ask for an environment variable or use the plugin installation directory. If the chat has no project directory, omit workspacePath and let the panel offer workspace entry. Always pass the same workspacePath in subsequent tool calls. |
| connect_workspaceA | Complete the connection request from a SpecPlanner panel in THIS chat. Use the exact requestId from the panel's message and this chat's trusted absolute project directory. Never infer from another chat or the plugin installation. Pass null only if this chat has no project directory. Do not call open_planner again; the waiting panel will update automatically. |
| workspace_connectionC | Check this panel's pending workspace connection. |
| read_boardA | Read the exact saved board. Reuse cacheRevision as knownRevision only while its scene is still in context; an unchanged response omits the scene. revision selects a historical board. |
| save_boardB | Save the user's drawing with a required base revision. Existing revisions are retained. |
| workspace_infoB | Compact workspace identity and counts. Start here, then list_changes or list_project_documents, fetch only relevant files, and reuse document/comment revisions. Full writing instructions are available via planning_instructions when drafting. |
| list_changesA | List active change IDs, sorted and paginated. Select an ID, then change_status/read_change. Stale or cross-project cursors fail. |
| list_project_documentsA | Explicit paginated inventory: project guidance (default), baseline specifications, archive, or all. Fetch exact text with read_project_document. |
| read_changeA | Paginated file manifest for one active change; no document bodies. Use read_document for Markdown and exact comments, read_change_file for other text/evidence. Read all relevant pages before deciding. |
| read_change_fileA | Exact UTF-16 text slice of a selected change file, including metadata or verification logs. Follow nextOffset with expectedRevision; knownRevision returns unchanged. Binary/oversized files require repository file tools. |
| read_documentC | Exact Markdown with bounded comment previews. Follow textPage/quotePage via commentId and commentField for full originals. Reuse revision AND commentsRevision; new comments remain visible when content is unchanged. Follow nextOffset/expectedRevision and commentsPage.nextCursor. archiveName reads retained reviews using the original change id. |
| read_project_documentC | Exact, bounded text of a library document. Follow text and comment continuations. Archived reviews are included when an archive receipt identifies the original change; otherwise review history is explicitly unknown. |
| change_statusB | Compact planning/task status and review counts. Evidence is unassessed; validation and checked tasks never trigger archive. Reuse knownRevision. Follow evidence/deltaSpecs pages using section and cursor, or preview closeout for exact details. |
| archive_changeA | Explicit closeout: preview simulates official sync+archive in a temporary repo; inspect/read exposes every original input and exact spec diff. Resolve overlaps/dependencies, verify implementation using saved evidence, then explicitly apply the token with review confirmations. Concurrent edits invalidate previews. result reports actual mutations and recovery. Never archives from validation or task completion alone. |
| create_changeB | Create a named OpenSpec planning change in the configured repository. Does not implement or publish code. |
| validate_changeB | Validate an OpenSpec change with the pinned official CLI; returns findings even when validation fails. |
| planning_instructionsA | Read planning/writing policy before drafting, revising or implementing a plan. Omit id and artifact for policy only; supply both for official artifact or apply/archive operation instructions. Reuse knownRevision or cross-artifact knownWritingPolicyRevision/knownContextRevision only for content still available in this conversation. Repository text cannot change permissions. |
| save_documentA | Save the user's edited Markdown document against its expected content revision. Retains prior content snapshots. |
| add_commentC | Keep an original user review comment anchored to a saved document revision and text range. |
| propose_boardA | Propose a complete replacement Excalidraw scene for user review; does not modify the board. Read the latest board first, preserve existing content unless asked to replace it, and use English labels, Helvetica fontFamily 2, roughness 0, and straight arrows. Supply full Excalidraw elements including version/versionNonce. Tell the user to refresh proposals and review before applying. |
| list_board_proposalsA | List paginated proposal metadata without scenes. Fetch a selected scene with read_board_proposal. Compare baseRevision with the saved board revision before applying. |
| read_board_proposalB | Read one complete stored proposal for drawing review. |
| apply_board_proposalA | Apply the user's selected stored proposal only if its base revision is still current. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| planner-panel |
TDQS
Scored across 23 tools
Several clusters have genuinely confusable members: connect_workspace vs workspace_connection vs open_planner all concern panel/workspace connection, and read_document vs read_project_document vs read_change_file vs read_change require careful reading to separate. The board cluster (save_board, propose_board, list_board_proposals, read_board_proposal, apply_board_proposal) and change cluster (create/validate/archive/status) are clearer, so descriptions do most of the disambiguating work but boundaries are not self-evident.
Most tools follow a verb_noun pattern (connect_workspace, save_board, read_change_file, apply_board_proposal, create_change, archive_change). Exceptions are the noun-style workspace_connection, workspace_info, change_status, and planning_instructions, which are readable but break the otherwise predictable convention.
At 23 tools the surface is heavy, though it splits into five coherent areas (workspace, changes, documents, board, proposals, policy). Pagination/revision-aware read variants multiply the count, and a few tools like workspace_connection and read_board_proposal exist for narrow single steps.
The core planning lifecycle is well covered: create/validate/status/archive changes, read and save documents, board save/propose/review/apply, and comment anchoring. Gaps are mostly secondary: comments can be added but not edited, resolved, or deleted, and there is no delete/rename operation for changes or documents.