AI Diagram Maker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADM_DEBUG | No | Set to '1', 'true', or 'yes' to log request parameters from the AI agent and the request payload sent to the AI Diagram Maker API. Logs go to stderr. | |
| ADM_API_KEY | Yes | Your AI Diagram Maker API key (used only for stdio transport) | |
| ADM_BASE_URL | No | Override for local/staging API; also used as the base for diagram URLs in tool responses | https://app.aidiagrammaker.com |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_diagram_from_textA | Generate a software engineering diagram from a natural language description. Use this tool when: the user asks to 'create a diagram', 'show me a flowchart', 'visualise the architecture', uses the keyword 'adm' or 'ai diagram maker', or asks for any visual representation of code, systems, processes or data flows. Supported diagram types: flowchart, sequence, ERD, system architecture, network architecture, UML, mindmap, workflow. Returns a link to view and edit the generated diagram in the browser. |
| generate_diagram_from_jsonA | Generate a diagram from a JSON structure. Use this tool when the user wants to visualise JSON data such as API responses, database schemas, dependency trees, configuration files, or any structured data. Pass the raw JSON string as |
| generate_diagram_from_asciiA | Convert an ASCII art diagram into a polished visual diagram. Use this tool when the user has an existing ASCII art representation of a system, flow, or architecture and wants it rendered as a proper diagram. Accepts box-drawing characters, arrow representations (-->, ==>), and plain text layouts. Returns a link to view and edit the generated diagram in the browser. |
| generate_diagram_from_imageA | Convert an image (whiteboard photo, screenshot, hand-drawn sketch) into a clean diagram. Use this tool when the user provides an image URL or base64-encoded image and wants it converted to a proper software engineering diagram. Accepts public image URLs or base64 data URIs (data:image/...;base64,...). Returns a link to view and edit the generated diagram in the browser. |
| generate_diagram_from_mermaidA | Convert a Mermaid diagram definition into a D2 diagram and return a PNG image. Use this tool when the user has existing Mermaid code (flowchart, sequenceDiagram, erDiagram, etc.) and wants it converted to D2 or rendered as an image. Pass the Mermaid source as content. Returns a link to view and edit the generated diagram in the browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Diagram Viewer |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose based on the input format: ASCII art, images, JSON, Mermaid code, or natural language text. The descriptions explicitly differentiate when to use each tool, with no overlap in functionality. An agent can easily select the appropriate tool based on the input type provided.
All tool names follow a consistent verb_noun pattern with 'generate_diagram_from_' as the prefix, followed by the specific input source (ascii, image, json, mermaid, text). This creates a predictable and readable naming convention throughout the tool set, making it easy for agents to understand the pattern.
With 5 tools, the server is well-scoped for its purpose of generating diagrams from various input formats. Each tool covers a distinct input type, and the count is neither too sparse nor overwhelming. This number allows comprehensive coverage without unnecessary complexity for the domain of diagram generation.
The tool set provides complete coverage for the server's purpose of generating diagrams from diverse input sources. It supports ASCII art, images, JSON, Mermaid code, and natural language text, covering all common ways users might want to create diagrams. There are no obvious gaps in the input formats supported, ensuring agents can handle a wide range of user requests.