Skip to main content
Glama

Related Servers

Alternatives to Neurons MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple coding agents to collaborate in a shared workspace with roles, messaging, concurrent file editing, task graphs, and live awareness of each other.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to join a secure agent-to-agent network for team collaboration, with tools for direct messaging, shared rooms, and approval-gated file/command requests.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to ask the user questions, receive written replies, share files, and hand tasks to other agent sessions — with every cross-agent request routed through human approval first. Sessions register themselves so they can be read, woken, and answered from a phone over a local-first, self-hosted setup.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.
      241
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.
      23 npm
      16
      Elastic 2.0

    TDQS

    B3.3/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes across messaging, memory, handoffs, reviews, sessions, and edit claims. Minor potential confusion exists between discover and inbox, and between handoff_get and session_read, but the descriptions clarify the boundaries well enough.

    Naming Consistency3/5

    The naming is readable and partly systematic, especially in the handoff_* and review_* families, but it mixes bare verbs (send, reply, disconnect), bare nouns (inbox, claims), and noun_verb compounds (recall_get, memory_save, session_read). The convention is not predictable across the full set.

    Tool Count5/5

    Fifteen tools is appropriate for a multi-agent collaboration server covering messaging, memory, handoffs, reviews, sessions, and edit locks. Each tool appears to serve a distinct workflow rather than duplicating another.

    Completeness4/5

    The surface covers core collaboration workflows well: discovery, inbox/send/reply, memory search/save, handoff publish/read, review request/read/submit, session reading, and claims. Some minor lifecycle gaps remain, such as richer memory deletion/management beyond archiving and limited review cancellation/cleanup operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues