Log inSubmit server
Network Diagram MCP logo

Network Diagram MCP

Build, edit, organize, and protect network topology maps through MCP tools connected to a local NetMap browser workspace.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Network Diagram MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "network-diagram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@den.dance/network-diagram-mcp"
      ],
      "env": {
        "NETMAP_MCP_PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @den.dance/network-diagram-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 7d ago.

Overview

The network-diagram-mcp MCP server connects an MCP-compatible agent to the NetMap browser application through a local stdio-to-WebSocket bridge. Agents can create and modify nodes, connections, sticky notes, sheets, layouts, canvas state, notes, and settings. Reach for it when you want an agent to build or maintain a visual network topology from structured information such as scanned hosts or inventory data. An open NetMap browser tab is required for tool calls to complete.

Use cases

  • Build a topology map from discovered hosts
  • Import an asset inventory into a visual network workspace
  • Group nodes by type or connected component
  • Maintain separate sheets for network environments
  • Lock a completed diagram against edits

Key features

  • MCP-controlled nodes and connections
  • Force, type, and connection-based layouts
  • Multi-sheet map management
  • Sticky notes and sheet-level notes
  • Local stdio-to-WebSocket bridge
  • Optional SSH, PostgreSQL, and Redis URL handlers

Tools37

What Network Diagram MCP lets your agent do. Expand a tool for its parameters.

Self-reported~804 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @den.dance/network-diagram-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads188Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed37Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Network Diagram MCP works

What network-diagram-mcp MCP server does

The network-diagram-mcp MCP server gives an MCP client control of a network topology workspace in NetMap. It can read the current map, create or modify nodes and connections, place sticky notes, manage multiple sheets, and adjust the visible canvas. Nodes can carry a type, name, IP address, and position; connections can include labels and colors.

The workspace supports several map-level operations. Agents can create, rename, switch, list, and delete sheets, while sheet locking prevents both MCP mutations and manual UI editing. Sheet notes and application settings can also be read or changed. Destructive operations such as clearing a map or deleting a sheet require explicit confirmation, and the final sheet cannot be deleted.

NetMap also provides browser-side network inventory features described by the project, including nmap XML and CSV imports, searchable node information, and export to JSON, PNG, or PDF. Those features are part of the connected application rather than separate tools listed in the MCP interface.

How it works

The network-diagram-mcp MCP server runs locally as a stdio process. The MCP client communicates with the process over standard input and output, while the process forwards requests over a local WebSocket connection to the open NetMap browser tab. NetMap applies the changes to its React state, so the diagram updates in the browser as calls are made.

Open https://map.den.dance/ before asking an agent to use the tools. The browser enables the MCP WebSocket connection by default in the documented v1.2-and-later setup. If no tab is connected, calls have no browser peer and time out. The connection can be disabled from NetMap settings under Integrations and AI Agent (MCP).

Layout support includes a basic grid or circle arrangement and three smarter strategies: force-directed placement, grouping by node type, and grouping connected components into zones. The force-directed option accepts a seed for deterministic results. The basic arrangement does not account for connections.

Setup and configuration

Install or run the package through npx:

Terminal
npx @den.dance/network-diagram-mcp

For Claude Desktop, add a server entry whose command is npx and whose argument is @den.dance/network-diagram-mcp. Claude Code can register the same command with claude mcp add, then verify it with claude mcp list. Cursor is also identified by the project as an MCP client.

The NETMAP_MCP_PORT environment variable changes the local WebSocket port from its default of 47821. The configured port must match the port set in NetMap's AI Agent integration settings.

The package also includes optional commands for registering SSH, PostgreSQL, and Redis URL handlers, detecting installed clients, and running a local daemon. For example, install --all registers all supported schemes, while serve starts the WebSocket and HTTP daemon on the configured port. These commands support the browser's in-app client picker but are separate from the default stdio MCP process.

Tools and capabilities

The exposed tools cover:

  • Reading and clearing map state, finding nodes by name, IP, type, or text, and applying layouts.
  • Adding, updating, moving, and deleting nodes and their connections.
  • Creating, editing, moving, and deleting sticky notes.
  • Creating, switching, renaming, listing, locking, and deleting sheets.
  • Setting zoom, panning the canvas, and fitting all nodes to the viewport.
  • Reading and writing sheet notes and application settings.

The network-diagram-mcp MCP server is suited to agent-assisted diagram creation, inventory visualization, topology cleanup, and controlled updates to an existing map. It is less suitable when the agent must work without a browser session or when the map must be hosted remotely by the MCP process itself.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Network Diagram MCP

network-diagram-mcp is an MCP server that connects compatible AI clients to the NetMap browser workspace through a local stdio-to-WebSocket bridge. Its main tools read and edit topology maps, including nodes, connections, sticky notes, sheets, layouts, canvas state, notes, and settings. An open NetMap tab is required for calls to work.

Install it with `npx @den.dance/network-diagram-mcp`, then add that command to your MCP client configuration. Claude Desktop uses a `command` and `args` entry, while Claude Code can use `claude mcp add netmap -- npx @den.dance/network-diagram-mcp`. Open the NetMap browser workspace afterward.

Yes, Cursor is named by the project as a supported MCP client. Configure the server using the command `npx @den.dance/network-diagram-mcp`, then open https://map.den.dance/ so the local bridge has a connected browser peer.

Tool calls time out when no NetMap browser tab is connected to the local WebSocket bridge. Open https://map.den.dance/ and keep its AI Agent MCP connection enabled. Also check that `NETMAP_MCP_PORT`, if changed, matches the port configured in NetMap settings.

Set the `NETMAP_MCP_PORT` environment variable to the desired local port and configure the same port in NetMap under Settings, Integrations, and AI Agent (MCP). The default port is `47821`.

Related MCP servers

All in Data Visualization All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNetwork Diagram MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/network-diagram-mcp?style=directory)](https://allmcps.com/mcp/network-diagram-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/network-diagram-mcp"><img src="https://allmcps.com/api/badge/network-diagram-mcp?style=directory" alt="Network Diagram MCP on AllMCPs" /></a>