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
      D
      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
      D
      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.
      1 npm
      8
      MIT

    • maestro

      daniel-madrid-07
      A
      license
      A
      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.
      20
      2
      MIT

    • agent-bridge

      rennerdo30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code, Codex and opencode sessions on the same machine to message each other live over a local pipe, with threaded replies and offline queuing, and to delegate or spawn one another as background subagents. Messages persist in SQLite and any running server can take over as broker, so peers stay reachable without a daemon.
      84 npm
      3
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 51 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes, such as pad_write vs. pad_append vs. pad_edit and todo_complete vs. todo_archive. However, with 51 tools there are several nuanced clusters whose boundaries depend on long descriptions, creating some risk of misselection.

    Naming Consistency4/5

    Names broadly follow a predictable snake_case domain_action pattern (todo_create, pad_read, agent_send, wake_cancel). Minor exceptions like help, whoami, and wake_when_idle deviate slightly, but the overall convention remains readable and consistent.

    Tool Count1/5

    51 tools is an extreme count for a single MCP server, even for a complex multi-agent orchestration domain. The surface spans many subdomains and likely includes low-frequency administrative operations that make the set heavy for an agent to navigate.

    Completeness5/5

    The tool surface covers lifecycle operations across agents, todos, pads, kv, leases, wakes, questions, projects, and auditing. State transitions like archive, withdraw, resume, park, prune, and cancel are present, leaving no obvious dead ends for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources