todiagram-mcp-windows-fix
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generateCodeDiagramA | Code-level or detailed component diagrams with key-value rows plus optional icons/images. Use for repositories, services, configs, or data-rich nodes. Note: setting imageUrl on a node hides all rows (label + image only); use iconUrl when you need both an icon and key-value fields. For high-level system visuals with mostly image nodes, use generateSystemDiagram. |
| generateDataDiagramA | Generate diagrams from structured data like JSON, YAML, CSV or XML. Use this tool specifically for visualizing raw data structures, configuration files, or API responses. |
| generateImageDiagramA | Convert an image (screenshot, diagram, whiteboard sketch, architecture drawing, etc.) into a ToDiagram custom format diagram. Analyzes the image to identify components, relationships, and hierarchical structure, then generates an equivalent diagram. |
| generateMermaidDiagramA | Use only when a user explicitly requests raw Mermaid syntax. Great for quick text-only flowcharts or when they need to edit Mermaid directly. For architecture, repositories, and anything that benefits from images/groups, prefer generateSystemDiagram or generateCodeDiagram. Supports optional Iconify icons (e.g., |
| generateSystemDiagramA | High-level system/architecture diagrams with grouped image/icon nodes (logos: or fa7-solid:). Keep fields minimal and favor visual nodes. Use nested parent/group nodes when it helps clarity—too many parents at root can get chaotic. Use this for repositories, platform overviews, services, and environment maps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| architecture-diagram | Generate a diagram based on the provided context. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/JehadurRE/todiagram-mcp-windows-fix'
If you have feedback or need assistance with the MCP directory API, please join our Discord server