Skip to main content
Glama
den-indance

NetMap — Network Diagram MCP

by den-indance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to NetMap — Network Diagram MCP

No user-submitted related servers found.

    Related Servers

    • omni-flow

      kanghelyu
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to create, customize, analyze and export relationship diagrams — theorem dependencies, paper maps, task RACI, org charts, conversation graphs — through 25 MCP tools, with cycle detection, centrality bottleneck reports, dependency closure and Mermaid/DOT/Markdown/JSON interop. Graphs stay local-first in a diff-friendly JSON source of truth and can be refined on a visual canvas.
      1
      -

    • Booboo

      jessymariau
      A
      license
      A
      quality
      A
      maintenance
      Open-source operational brain that fuses an AI system's agents, memory, knowledge and automations into one rooted, privacy-walled graph, served over MCP with stats, search, node dossiers, neighbors and pathfinding. The same snapshot also renders up to a million nodes in a 3D browser view.
      8
      1
      MIT

    • buddy

      enki-run
      A
      license
      Not graded
      quality
      F
      maintenance
      Agent-first knowledge graph MCP server that provides 25 tools for managing a knowledge graph with nodes and edges, plus a human-readable dashboard for LLMs and AI agents.
      361 npm
      Apache 2.0
    • Heym by heymrun

      Heymofficial

      heymrun
      F
      license
      C
      quality
      A
      maintenance
      Self-hosted, source-available AI workflow automation platform. Build multi-agent, RAG, and tool-using pipelines on a visual canvas and publish any workflow as an MCP server (stdio/SSE/Streamable HTTP). Also an MCP client via the agent node.
      2
      1,251
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 44 tools

    Disambiguation3/5

    While descriptions are detailed, several tools overlap in purpose: map_get_state, map_get_sheet_data, map_export_sheet, and map_export all return map data; map_arrange and map_suggest_layout both auto-layout; map_find_node, map_search, and map_get_nodes_by_type all query nodes. Explicit notes clarify some boundaries, but an agent could easily choose the wrong tool without careful reading.

    Naming Consistency4/5

    All tools share the 'map_' prefix and use snake_case throughout, with most following a verb_noun pattern (map_add_node, map_delete_connection). Minor deviations include bare verbs like map_clear, map_arrange, map_search, and map_export, but these are limited and the overall pattern is predictable.

    Tool Count2/5

    At 44 tools, the server is significantly over the typical range for an MCP server. While the domain is broad, many tools could be consolidated (e.g., map_get_state vs map_get_sheet_data, map_arrange vs map_suggest_layout) to reduce cognitive load. The high count feels heavy even with the expansive feature set.

    Completeness5/5

    The tool surface is remarkably comprehensive, covering full CRUD for nodes, connections, stickies, and sheets, plus view management, settings, search, import (CSV, nmap, JSON), export (JSON/PNG/PDF), layout algorithms, selection, and bulk operations. The domain of network diagram management is well-served with no major dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources