@perssona/orchestrator
OfficialServer 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_connected_terminalB | Create a Perssona terminal node near a source node and connect it visually. If sourceNodeId is omitted, use the selected canvas node. |
| create_codex_terminal_from_agentA | Create a connected Codex terminal using an agent preset. If sourceNodeId is omitted, use the selected canvas node. |
| create_claude_terminal_from_agentC | Create a connected Claude terminal using an agent preset. If sourceNodeId is omitted, use the selected canvas node. |
| send_annotation_to_connected_terminalsA | Send an Annotation node content to all connected terminal nodes. If annotationNodeId is omitted, use the selected annotation node. |
| send_text_to_connected_terminalsB | Send text from a source node to all connected terminal nodes. If sourceNodeId is omitted, use the selected canvas node. |
| get_selected_nodeA | Return the currently selected canvas node, if any. |
| list_canvas_nodesA | Return the nodes and edges currently present in the active canvas. |
| list_orchestrator_presetsA | List the workspace presets for models, agents, and workflows configured in Perssona. |
| connect_nodesC | Create a connection edge between two canvas nodes. |
| create_annotation_nodeB | Create an annotation node. If sourceNodeId is omitted, use the selected node or create it near the current viewport. |
| update_annotation_nodeC | Update an existing annotation node. If nodeId is omitted, use the selected annotation node. |
| send_text_to_terminalC | Send text directly to a specific terminal node. |
| remove_nodeA | Remove a canvas node and its connected edges. If nodeId is omitted, use the selected node. |
| add_node_to_gridC | Add an existing canvas node to the grid view. |
| focus_nodeB | Select a canvas node and center the viewport on it. If nodeId is omitted, use the selected node. |
| disconnect_nodesC | Remove one or more connection edges between two canvas nodes. |
| get_connected_nodesA | Return nodes and edges connected to a node. If nodeId is omitted, use the selected node. |
| open_nodes_in_gridA | Open one or more nodes in the grid view. If nodeIds is omitted, use the selected nodes. |
| create_agent_pairC | Create two connected LLM terminals for parallel roles like design and corrections. |
| run_workflow_from_annotationB | Use an annotation, a selected node, or a direct prompt as the entrypoint for a workflow, creating agents, opening them in the grid, and sending the initial prompts. |
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 20 tools
Most tools have distinct purposes, but there is some overlap among the various 'create' tools (e.g., create_agent_pair, create_claude_terminal_from_agent, create_connected_terminal) that could cause confusion if descriptions are not read carefully. However, descriptions are clear enough to differentiate them.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., add_node_to_grid, connect_nodes, run_workflow_from_annotation). No mixing of conventions or inconsistent styles.
With 20 tools, the server covers a broad canvas orchestration domain including node management, connections, terminals, and workflows. While on the higher side, each tool serves a specific purpose and the count feels justified.
The tool set covers core operations: CRUD for annotation nodes, connections, terminals, grid management, and workflow execution. Minor gaps exist (e.g., no direct update for non-annotation nodes, no node renaming), but the surface is largely complete for its stated purpose.