AWS, Azure and GCP architecture diagrams with official icons, reviews, Terraform and GCP import
Connect Runs on your machine
claude mcp add architecture-diagrams -e ARCH_DIAGRAM_OUTPUT_DIR=<ARCH_DIAGRAM_OUTPUT_DIR> -e ARCH_DIAGRAM_INPUT_ROOTS=<ARCH_DIAGRAM_INPUT_ROOTS> -- uvx arch-diagram-mcp==1.2.0{
"mcpServers": {
"architecture-diagrams": {
"command": "uvx",
"args": [
"arch-diagram-mcp==1.2.0"
],
"env": {
"ARCH_DIAGRAM_OUTPUT_DIR": "<ARCH_DIAGRAM_OUTPUT_DIR>",
"ARCH_DIAGRAM_INPUT_ROOTS": "<ARCH_DIAGRAM_INPUT_ROOTS>"
}
}
}
}{
"mcpServers": {
"architecture-diagrams": {
"command": "uvx",
"args": [
"arch-diagram-mcp==1.2.0"
],
"env": {
"ARCH_DIAGRAM_OUTPUT_DIR": "<ARCH_DIAGRAM_OUTPUT_DIR>",
"ARCH_DIAGRAM_INPUT_ROOTS": "<ARCH_DIAGRAM_INPUT_ROOTS>"
}
}
}
}{
"servers": {
"architecture-diagrams": {
"type": "stdio",
"command": "uvx",
"args": [
"arch-diagram-mcp==1.2.0"
],
"env": {
"ARCH_DIAGRAM_OUTPUT_DIR": "<ARCH_DIAGRAM_OUTPUT_DIR>",
"ARCH_DIAGRAM_INPUT_ROOTS": "<ARCH_DIAGRAM_INPUT_ROOTS>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
ARCH_DIAGRAM_OUTPUT_DIROptional | Folder for rendered diagrams (default: ~/architecture-diagrams) |
ARCH_DIAGRAM_INPUT_ROOTSOptional | Folders the server may read Terraform or inventory files from, separated by the OS path separator |
Details
| Package | [email protected] (PYPI, stdio) |
| Package | [email protected] (NPM, stdio) |
| First published | 27 Oct 2026 |
| Last updated | 27 Oct 2026 |
| Registry name | io.github.apatilgtn/architecture-diagrams |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.