Network Diagram Mcp
Let your agent build and update network topology diagrams from nmap scans or CSV imports, with a local bridge to NetMap and optional SSH workflows.
Overview
io.github.den-indance/network-diagram-mcp is an Operate-phase MCP server that lets agents construct and update network topology diagrams via NetMap, including nmap/CSV import and a local bridge port.
What is this MCP server?
- MCP-driven network topology editing with Claude as the diagram builder
- nmap and CSV import paths to populate nodes and links quickly
- Local WebSocket bridge on NETMAP_MCP_PORT (default 47821) matching NetMap MCP Agent Bridge settings
- npm package @den.dance/network-diagram-mcp v1.0.7, stdio transport
- One-click SSH workflow called out for operating live network contexts from the diagram tool
- npm package @den.dance/network-diagram-mcp version 1.0.7
- stdio MCP transport
- NETMAP_MCP_PORT environment variable with documented default 47821
What problem does it solve?
Network layout lives in scattered nmap logs and spreadsheets, so agents and humans lack a single topology source to reason about connectivity and changes.
Who is it for?
Solo devops-minded builders documenting homelabs, small client networks, or internal environments who already use or can install NetMap.
Skip if: Builders who only need cloud architecture in a SaaS console, or teams without permission to scan or diagram real networks.
What do I get? / Deliverables
Discovery data flows into an agent-maintained diagram with a configured local bridge, so infrastructure discussions and runbooks reference one updated map.
- Agent-editable network topology diagram in NetMap
- Imported host/link inventory from nmap or CSV
- Aligned local MCP bridge on configurable port (default 47821)
Recommended MCP Servers
Journey fit
Documenting and evolving network layout is an Operate concern once systems exist in production or homelab environments. Infra subphase covers topology maps, discovery imports, and how hosts connect—what this editor and MCP bridge automate.
How it compares
Topology and discovery documentation MCP—not a cloud deploy provisioner or generic diagramming skill without network import.
Common Questions / FAQ
Who is network-diagram-mcp for?
Indie operators and developers who maintain network maps and want Claude or similar agents to import scans and edit topology through MCP.
When should I use network-diagram-mcp?
Use it during Operate when onboarding new hosts, after nmap discovery, or when you need an accurate diagram before changes or incident response.
How do I add network-diagram-mcp to my agent?
Install @den.dance/network-diagram-mcp, add it as a stdio MCP server in your agent config, set NETMAP_MCP_PORT to match NetMap Settings → MCP Agent Bridge, then connect NetMap.