Skip to main content
Glama

Related Servers

Alternatives to Mind Map MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create, edit, and export flowcharts through a local web-based editor with visual drag-and-drop, real-time sync, and 14 MCP tools for full node/edge CRUD.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents a live, persistent diagram canvas they can draw on, inspect via screenshots, and refine element by element, then export as editable .excalidraw files to commit alongside code. Supports architecture diagrams and flowcharts through a CLI, MCP tools, or REST API.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to directly inspect and edit an already-open desktop mind-map canvas—searching maps, managing documents, reading/editing/moving/deleting nodes, inserting rendered LaTeX formulas, and taking screenshots—with changes reflected live and synced to the cloud.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Create visual whiteboards, diagrams, flowcharts, and project plans from AI conversations. 17 MCP tools for board management, element creation, and real-time collaboration.
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    visualize (create) and edit_diagram (modify) have clearly separate roles, and get_diagram reads state. The remaining three (load_state, save_state, export) are view-side plumbing whose boundaries are fuzzier — load_state's description ('reads the diagram, or learns it is up to date') is vague and overlaps conceptually with get_diagram.

    Naming Consistency3/5

    edit_diagram, get_diagram, load_state, save_state follow a consistent verb_noun pattern, but visualize and export are bare verbs with no noun object, and the noun spelling varies (diagram vs. state). Readable but not uniform.

    Tool Count4/5

    Six tools is a reasonable scope for a diagram server. However, three of the six (load_state, save_state, export) are client/view plumbing rather than agent-facing capabilities, which makes the set feel slightly padded relative to the core visualize/edit/get trio.

    Completeness4/5

    The core lifecycle is covered: create (visualize), read (get_diagram), update (edit_diagram), and export. Missing a delete/remove-diagram operation and any listing of existing diagrams, but these are minor gaps an agent can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues