@drawx/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAWX_API_KEY | Yes | Your DrawX API key (starts with drawx_live_) | |
| DRAWX_API_BASE | No | Override the API base URL (default https://getdrawx.com/api/v1). Useful for staging. |
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 |
|---|---|
| generate_diagramA | Generate a draw.io (diagrams.net) diagram from a natural-language description. Returns complete mxfile XML you can save as a .drawio file or paste into diagrams.net. Pass previousXml to modify an existing diagram. |
| architect_designA | Run the DrawX Architect Co-Pilot: from a brief, produce a High-Level Design diagram (optionally a Low-Level Design and a written design document). Returns the diagram XML and rationale. Best for 'design me an architecture for X' requests. |
| whoamiA | Show the DrawX account tied to the configured API key, its plan, API tier, and remaining monthly API quota. Useful to confirm the key works before generating. |
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 3 tools
The tools 'generate_diagram' and 'architect_design' both generate diagrams but serve distinct purposes: general diagram creation vs. architectural design with documentation. 'whoami' is unrelated. Descriptions clearly differentiate the two diagram tools, though some overlap remains for architecture diagram requests.
Tool names are all lowercase with underscores, but patterns differ: 'generate_diagram' (verb_noun), 'architect_design' (noun_noun or unusual verb_noun), and 'whoami' (standalone command). The mix of conventions makes the set less predictable.
With 3 tools, the surface is minimal but well-scoped for the server's purpose of generating diagrams from natural language. Each tool serves a core function: general generation, architectural design with documentation, and account verification. No tool feels redundant or missing.
The server covers diagram generation and modification (via previousXml) and includes architectural design with written output. It lacks tools for listing, deleting, or converting diagrams, which is acceptable given the focus on generation. Minor gap in retrieving non-XML outputs.