it-architecture
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ITARCH_OUTPUT_DIR | No | Directory where output SVG files are saved | ~/architecture-diagrams |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_authoring_guideA | Read this first. Returns the complete notation for describing an IT architecture (compact DSL + equivalent JSON), the available styles, group kinds and a worked example. No arguments. |
| list_stylesA | List the available drawing styles (cloud, azure, material, c4, blueprint, whiteboard, minimal, neon, slate) with a description of each look. |
| list_node_typesA | List every component icon (server, database, queue, k8s, firewall, ...) with its category and the aliases that map onto it. |
| validate_architectureA | Parse a diagram without drawing it. Reports every syntax/reference error at once, plus warnings about orphan nodes, empty groups and unknown icon types. Cheap to call before rendering. |
| render_architectureB | Draw an IT architecture and save it as a standalone .svg file (optionally in several styles at once). Layout, routing and grouping are automatic - never supply coordinates. Returns the absolute file paths. |
| render_all_stylesA | Render the same architecture once per available style into one directory, so a human can pick the look they want. Files are suffixed with the style name. |
| preview_architectureA | Return the SVG markup inline instead of writing a file. Use when the client can display or post-process SVG directly. |
| convert_notationA | Convert a diagram between the compact DSL and the JSON spec (both directions), normalising it on the way. Useful for editing a diagram that was written in the other notation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
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/slajzad/mcp-architecture'
If you have feedback or need assistance with the MCP directory API, please join our Discord server