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

    • agent-chat

      TobiasCoding
      A
      license
      B
      quality
      C
      maintenance
      Enables Claude Code and Codex agents to exchange durable room-based messages through a shared local chat room, with incremental reads, recipients, structured metadata, and SQLite persistence over MCP stdio.
      4
      MIT

    • 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.
      5 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.
      36 npm
      MIT

    • agent-bus

      onlybrezel
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex and Claude Code sessions to discover one another and exchange direct, group, and threaded messages with read receipts, backed by a local SQLite store and native notifications that wake the receiving client. Supports optional end-to-end encrypted relay messaging between trusted machines while local delivery continues to work offline.
      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.
      36 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

    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