Skip to main content
Glama
cmgmyr

hive

by cmgmyr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to hive

No user-submitted related servers found.

    Related Servers

    • memtree

      aiagate
      F
      license
      Not graded
      quality
      C
      maintenance
      Collects session JSONL from Codex and Claude Code into local SQLite memory, exposed through MCP with tools for memory context, search, get, put, forget, sleep, and status.
      -

    • Brain MCP

      DevvGwardo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables inter-session communication and coordination for multiple Claude Code instances through a shared SQLite database. Supports real-time messaging, shared state management, and resource locking to facilitate parallel development workflows between AI agents.
      5 npm
      8
      MIT

    • maestro

      daniel-madrid-07
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to launch and supervise multiple concurrent Claude Code sessions in tmux, sending them briefs, reading their progress, answering their prompts, and managing isolated git worktrees.
      1
      MIT

    • agent-bridge

      suneel944
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.
      MIT

    • agent-relay

      CyberArchitecta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables running both Claude Code and Codex locally with a shared task board, session resume, cross-agent handoff, and an MCP bridge for inter-client messaging and task/context inspection.
      MIT
    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 45 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action combination: projects, agents, pads, todos, kv, leases, and wakes are cleanly separated. Even close pairs like agent_park/agent_close and pad_archive/pad_delete are explicitly differentiated by lifecycle semantics, so misselection is unlikely.

    Naming Consistency5/5

    Tool names consistently follow a noun_action pattern: project_list, agent_spawn, pad_append, todo_complete, kv_set, wake_cancel. The only outliers are help and whoami, which are conventional utility commands and do not break the overall pattern.

    Tool Count2/5

    45 tools is a very large surface for one MCP server and exceeds the 25-tool threshold for 'too many'. While each tool appears purposeful, the set would be easier for an agent to navigate if split into separate servers by resource domain, such as agents, todos, pads, and wakes.

    Completeness4/5

    Most resources have strong lifecycle coverage: pads and todos support create/read/update/archive/delete, agents have spawn/resume/park/status/send/close, and KV and wakes have full get/set/list/delete or cancel flows. The main gap is leases, which can be acquired and released but not listed or inspected, and project deletion is limited to pruning empty projects.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources