Skip to main content
Glama
chldbwnstm

VisualizeBetter

by chldbwnstm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to VisualizeBetter

No user-submitted related servers found.

    Related Servers

    • MemoryGraph

      memory-graph
      A
      license
      Not graded
      quality
      A
      maintenance
      A graph-based MCP server that provides AI coding agents with persistent memory to store patterns, track complex relationships, and retrieve knowledge across sessions. It leverages graph structures to handle temporal queries and relational paths that traditional vector stores often miss.
      247
      MIT

    • NOMIK

      willFreed1
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-native code intelligence graph that builds a persistent knowledge graph of your codebase in Neo4j and exposes it to AI assistants via MCP, enabling contextual code analysis, impact analysis, and dependency tracking.
      23
      -

    • portuni

      honzapav
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides a shared graph of an organization's projects, processes, areas, and principles, enabling consistent context for tools and AI agents.
      2
      Apache 2.0

    • relation-net

      shaoqing9890
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables structured knowledge and relationship modeling through a persistent network graph, with tools for linking structures, running six-dimensional comparisons, writing confidence scores, and learning from GitHub or computer-science fundamentals via natural-language MCP interactions.
      -
    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

    B3.1/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (push vs update vs delete vs list vs get), but some overlap exists: clear_layer/clear_all/delete_node/delete_edge all delete things, and get_graph_summary/list_nodes/search all provide graph overviews. The descriptions help disambiguate, but the boundaries between clear_layer and delete_node could confuse an agent.

    Naming Consistency4/5

    The naming is predominantly verb_noun (push_node, list_edges, delete_finding, load_snapshot) with consistent snake_case. Minor deviations: undo/redo are bare verbs, and focus_on/suggest_filter use prepositions, but the overall pattern is predictable and readable.

    Tool Count3/5

    43 tools is on the heavy side for a graph visualization server. The scope is broad (graph CRUD, findings, snapshots, view state, events, import/export), so each tool has a role, but the count exceeds the typical well-scoped range and will increase agent selection overhead.

    Completeness4/5

    The surface covers the full graph lifecycle (create/read/update/delete for nodes, edges, findings), plus snapshots, import/export, and view-state awareness. Minor gaps: no explicit tool for listing layers or managing citations beyond adding them, and no bulk delete for edges, but agents can work around these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources