ExcaliDash MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Host loopback port for Docker Compose. | 9003 |
| MCP_HTTP_HOST | No | Internal HTTP bind address for HTTP mode. | 0.0.0.0 |
| MCP_HTTP_PORT | No | Internal HTTP port for HTTP mode. | 8080 |
| EXCALIDASH_URL | Yes | ExcaliDash public or internal URL. The /api can be omitted. | |
| EXCALIDASH_TOKEN | No | Alternate API key alias for compatibility with previous settings. | |
| MCP_MAX_SESSIONS | No | Maximum number of concurrent MCP sessions. Returns 429 if exceeded. | 64 |
| EXCALIDASH_API_KEY | Yes | Account API key with Read drawings and Write drawings scopes. | |
| MCP_MAX_BODY_BYTES | No | Maximum HTTP request body size. | 10485760 |
| MCP_SESSION_IDLE_MS | No | Idle session cleanup timeout in milliseconds. | 1800000 |
| EXCALIDASH_DRAWING_ID | No | Default drawing ID to select at startup. |
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 |
|---|---|
| list_drawingsA | List ExcaliDash drawings available to the account API key. Use this before selecting a drawing. |
| select_drawingA | Select an Excalidraw drawing as the default target for subsequent tools in this MCP process. |
| get_selected_drawingA | Return the drawing currently selected by this MCP process. |
| create_drawingB | Create a new empty Excalidraw drawing and optionally select it as the default target. |
| get_drawing_summaryA | Read a compact structural summary of a drawing. Uses drawingId when provided, otherwise the selected drawing. |
| inspect_drawing_elementB | Inspect one element and its bound children. Uses drawingId when provided, otherwise the selected drawing. |
| apply_drawing_opsA | Atomically apply up to 50 semantic operations. Uses drawingId when provided, otherwise the selected drawing. Read the summary first. |
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 7 tools
Each tool has a distinct purpose: selection state vs. catalog listing vs. selection mutation vs. creation vs. summary reading vs. element inspection vs. operations application. There is no overlapping or ambiguous tool that could cause an agent to misselect. The descriptions clearly delineate responsibilities.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like get, list, select, create, inspect, and apply. The pattern is predictable and uniform across the set, making it easy for an agent to infer behavior from the name.
With exactly 7 tools, the set is well-scoped for a drawing management MCP. Each tool serves a clear, non-redundant function, and the count is neither too sparse nor overwhelming for the stated purpose.
The toolset covers listing, creating, selecting, reading summaries, inspecting elements, and applying operations, which are core workflows. A notable gap is the absence of a delete_drawing tool, and there is no explicit tool for updating drawing metadata, but these are minor and can be worked around.