planist-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLANIST_API_HOST | Yes | The host URL of the Planist API. For example: http://127.0.0.1:8080 | http://127.0.0.1:8080 |
| PLANIST_GRANT_TOKEN | Yes | The token used to authorize planist-mcp to propose page edits. This is the AI Capability Grant token. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| planist_list_pagesA | List all accessible pages (Docs, Sheet, Slide, Edgeless, Design, Dashboard) in the Planist project workspace. |
| planist_read_pageA | Read the AST, Markdown, or structural block representation of a specific Planist page by its Stable ID. |
| planist_propose_page_editA | Submit a page edit proposal (LivePageProposal) to Planist for human review and atomic transaction write-back. |
| planist_list_variablesA | List all reactive typed variables in the Project variable substrate (bound to Sheet cells, Dashboard KPIs, Docs, and Workflows). |
| planist_get_variableA | Get the current value, type contract, and binding references for a specific project variable. |
| planist_update_variableA | Update a typed project variable value. This triggers reactive UI updates across bound Sheet cells, Dashboard widgets, and Docs (Execute -> Variable -> Plan loop). |
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 6 tools
Each tool targets a distinct operation on either pages or variables: list/read/propose for pages, and list/get/update for variables. There is no overlap or ambiguity between them.
All tool names follow the consistent planist_<verb>_<noun> pattern using snake_case. Verbs are clear and specific (list, read, get, propose, update), making the naming predictable and coherent.
With six tools, the server is well-scoped for managing pages and variables. The count is within the ideal 3-15 range and each tool serves a clear purpose without unnecessary bloat.
The server covers read, list, and update operations for both pages and variables, but lacks any creation or deletion capabilities. This is a notable gap in the resource lifecycle, though the propose-edit workflow adds a distinct review step for page modifications.