Developer · Local MCP server
Network Diagram MCP
Network topology editor - Claude builds diagrams via MCP. nmap/CSV import, one-click SSH.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.den-indance/network-diagram-mcp- Version
- 1.0.7
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-22
- Updated
- 2026-05-22
- Publisher
- den-indance (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/den-indance) · how
- Repository
- github.com/den-indance/network-diagram-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @den.dance/network-diagram-mcp | 1.0.7 | stdio |
How to connect Network Diagram MCP
Network Diagram MCP runs locally from a Node.js package published to the npm registry: @den.dance/network-diagram-mcp version 1.0.7. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @den.dance/network-diagram-mcp@1.0.7. It reads the environment variable NETMAP_MCP_PORT; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"network-diagram-mcp": {
"command": "npx",
"args": [
"-y",
"@den.dance/network-diagram-mcp@1.0.7"
],
"env": {
"NETMAP_MCP_PORT": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from den-indance (GitHub)
| Server | Runs |
|---|---|
| Google Trends MCPGoogle Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup. | Local · stdio |
| Shopify MCP ProShopify MCP server with real analytics (ShopifyQL), auto-refresh auth, and Shopify API 2026-04. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Netcafe DevkitJSON/YAML, regex, diff, JWT, SQL dialects - the keyless millisecond ops an agent needs mid-task. | Remote · HTTPLive check: ✓ handshake |
| NetdataReal-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection. | Remote · HTTPLive check: sign-in required |
| Netintel MCPMCP server for NetIntel - DNS, SSL, WHOIS, email security, OSINT via x402 micropayments. | Local · stdio |
| NetworkDNS, IP info, SSL, WHOIS, ping for AI agents. | Local · stdio |
| Neura Relay MCPGovern proposed Action Cards with Decision Receipts before developer-owned execution. | Remote · HTTPLive check: sign-in required |
| Neural DraftNeural Draft MCP - CMS, blog, bookings, galleries, commerce. 38 tools. | Local · stdio |
| NeuralBrainNeuralBrain MCP Server - RAG, Vector Memory, LLM Routing, Agent Identity, x402 Payments. | Remote · HTTPLive check: ✗ no handshake |
| Neurarch MCPReads a PyTorch.py, a Neurarch graph, or a HF repo; agents inspect, lint, verify and rank designs. | Local · stdio |