Azure Diagram MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_LOG_LEVEL | No | Log level for FastMCP (e.g., ERROR, INFO). Default is INFO if not set. | INFO |
| DIAGRAM_COPILOT_MODEL | No | Model override (default: 'gpt-4.1'). | |
| DIAGRAM_COPILOT_API_KEY | No | API key for the LLM provider. | |
| DIAGRAM_COPILOT_BASE_URL | No | API endpoint URL for the LLM provider. | |
| DIAGRAM_COPILOT_WIRE_API | No | API wire format: 'completions' or 'responses'. | |
| DIAGRAM_COPILOT_PROVIDER_TYPE | No | LLM provider type: 'openai', 'azure', or 'anthropic'. Required only when using Copilot SDK with BYOK. | |
| DIAGRAM_COPILOT_AZURE_API_VERSION | No | Azure API version (default: '2024-10-21'). |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_diagramB | Generate a diagram from Python code using the diagrams package DSL. |
| refresh_diagramC | Regenerate a diagram from updated code (app-only tool). |
| get_diagram_examplesC | Get example diagram code for the specified diagram type. |
| list_iconsB | List available diagram icons organized by provider and service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_diagram_viewer | Serve the interactive diagram viewer HTML app. |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: generating diagrams, fetching examples, listing icons, and refreshing. No overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case, making the set predictable and easy to navigate.
With 4 tools, the set is well-scoped for generating and managing diagrams, though slightly thin for a full lifecycle.
Core operations are covered, but missing features like editing, exporting, or deleting diagrams create gaps that agents may need to work around.