Calliope MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport. Overrides CALLIOPE_MCP_PORT if set. | |
| URANIA_URL | No | URL of the Urania capture service. | http://urania:8202 |
| CALLIOPE_MCP_PORT | No | Port for HTTP transport if PORT not set. | 8204 |
| CALLIOPE_MCP_BACKEND | No | Backend type. Set to 'fixture' for standalone server without Urania. | |
| CALLIOPE_URANIA_WIRED | No | Flag to enable live Urania transport. |
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 |
|---|---|
| read_bodyA | Resolve a plan node's body — its prose sections, sorted by order key. Returns { sections: [{ id, text, orderKey }] }; a node with no body returns an empty list. |
| write_bodyA | Replace a plan node's whole body with the given sections, in display order. The substrate mints fresh order keys and copy-on-writes changed prose. Returns { ok, count }. |
| append_sectionA | Append one new section to the end of a plan node's body. Returns the appended { section } and the new body { count }. |
| edit_sectionA | Replace the prose of a single section (copy-on-write), keeping its position and every other section untouched. Returns the edited { section }. |
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 4 tools
Each tool has a clearly distinct purpose: appending a new section, editing a single section's prose, reading all sections, and replacing the entire body. No overlap or confusion.
All tool names follow the consistent verb_noun pattern: append_section, edit_section, read_body, write_body. No mixing of styles.
With 4 tools, the server is well-scoped for managing sections of a plan node. Each tool serves a fundamental operation without unnecessary bloat.
The set covers read, create (append), update (edit), and full replacement (write_body), but lacks a dedicated delete_section tool. However, deletion can be achieved via write_body by omitting a section, so the gap is minor.