Draw.io Diagram Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAWIO_OUTPUT_DIR | No | Specifies the directory where diagram files will be saved. If not set, files are saved to the current working directory. |
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 |
|---|---|
| create_diagramB | Create various types of diagrams (flowchart, sequence, network, erd, custom) and save to a file. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as creating diagrams of various types.
The single tool name 'create_diagram' follows a clear verb_noun pattern. Consistency is inherent with one tool.
A single tool for diagram creation is too few; the scope implies needs like listing, editing, or exporting diagrams. This falls into the 'too few' category.
Only creation is covered, with no tools for reading, updating, deleting, or managing diagrams. The surface is severely incomplete for a diagram server.