Architecture Diagrams MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const probe = spawnSync(cmd, ["--version"], { stdio: "ignore", shell: process.platform === "win32" });

    out = subprocess.run([dot, "-V"], capture_output=True, text=True, timeout=15)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add architecture-diagrams -- npx -y arch-diagram-mcp

{
  "mcpServers": {
    "architecture-diagrams": {
      "command": "npx",
      "args": [
        "-y",
        "arch-diagram-mcp"
      ]
    }
  }
}

[mcp_servers.architecture-diagrams]
command = "npx"
args = ["-y", "arch-diagram-mcp"]

{
  "mcpServers": {
    "architecture-diagrams": {
      "command": "npx",
      "args": [
        "-y",
        "arch-diagram-mcp"
      ]
    }
  }
}

{
  "servers": {
    "architecture-diagrams": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "arch-diagram-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: ARCH_DIAGRAM_OUTPUT_DIR (Folder for rendered diagrams (default: ~/architecture-diagrams)), ARCH_DIAGRAM_INPUT_ROOTS (Folders the server may read Terraform or inventory files from, separated by the OS path separator).