Skip to main content
Glama
reteren

hive-mcp

by reteren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to hive-mcp

No user-submitted related servers found.

    Related Servers

    • tldraw MCP

      talhaorak
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read, write, and search local tldraw (.tldr) files, providing a persistent visual scratchpad for diagramming and note organization. It supports full CRUD operations on canvas shapes and metadata management for local canvas files.
      23 npm
      3
      MIT

    • infinite-canvas

      skundu42
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models and browser users to collaboratively create and edit a shared freeform canvas of positioned cards and directed connections, with tools for adding, updating, linking, and exporting boards as JSON or SVG.
      -

    • mcp-vault-reader

      LucasRocha179
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search, read, and traverse Markdown note vaults (Obsidian-compatible) with full-text search, backlinks, knowledge graphs, and a persistent memory system for cross-session context.
      16
      8 npm
      4
      MIT

    • obsidian-mcp-server

      huaqing0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading, writing, searching, and surgical editing of Obsidian vault notes, tags, and frontmatter, plus workspace control, vault structure management, and native Excalidraw automation.
      3,187 npm
      Apache 2.0
    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 25 tools

    Disambiguation4/5

    Most tools target clearly distinct resource+action pairs (create/update/delete/move/arrange nodes, CRUD for links and zones, trash/archive handling). A few boundaries blur: move_nodes vs arrange_nodes vs update_nodes (which also moves/resizes), and search_nodes vs list_nodes (which takes a text query) vs get_nodes, though descriptions clarify the intended use.

    Naming Consistency4/5

    Almost all tools follow a clean snake_case verb_noun pattern (create_nodes, list_links, update_zone, delete_links). The main blemish is pluralization drift within the same resource (create_zone singular vs list_zones/delete_zones plural) and describe_node_kinds, but overall it is predictable and readable.

    Tool Count3/5

    25 tools is at the heavy end for the apparent scope. The domain (nodes, links, zones, trash, archive, files, view, project) is genuinely rich and most tools earn their place, but full CRUD replicated across nodes/links/zones plus many utility verbs makes the surface feel crowded and could be consolidated.

    Completeness4/5

    Coverage is strong: full CRUD across nodes, links, and zones, plus trash listing/restore, import, view focus, undo, save, status, kind introspection, and list/get/search. The one notable dead end is archive handling — list_archive exists but there is no restore/unarchive operation, and no permanent delete or empty-trash.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources