Skip to main content
Glama
MiiKiyoshi

agent-channel-mcp

by MiiKiyoshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-channel-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      9 npm
      8
      MIT

    • agent-bridge

      Sora-bluesky
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables bidirectional messaging between Claude Code and Codex Desktop through a SQLite-backed bus, so messages sent from either side appear in the other's chat pane, with acknowledgement and redelivery semantics.
      4 npm
      MIT

    • hato

      severzemlya
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables inter-session messaging for Claude Code, allowing sessions on different machines to send messages to each other, with delivery as user turns and support for offline queuing.
      323 npm
      MIT

    • mcp-comms

      ahmeda14960
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables multiple AI agents to communicate and coordinate via a shared SQLite-backed message log, supporting directed messages, broadcasts, and session discovery.
      -

    • claude-session-bus

      Catweazle74
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coordination and communication between multiple Claude Code sessions across machines via a chat server, providing tools for sending messages, waiting for responses, and managing session status.
      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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action in the room lifecycle: joining, sending messages, renaming, and leaving. There is no overlap in purpose; join's complexity does not confuse it with other operations.

    Naming Consistency5/5

    All tool names are single imperative verbs in lowercase (join, send, rename, leave), following a predictable and consistent convention throughout.

    Tool Count5/5

    Four tools is well-scoped for a basic agent channel. Each tool earns its place by covering a necessary room interaction without redundancy.

    Completeness4/5

    The surface covers join, send, rename, and leave, which is most of the chat lifecycle. An explicit message-retrieval tool is missing, but the join response points to a waiter process that likely delivers incoming messages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources