Skip to main content
Glama
TobiasCoding

agent-chat

by TobiasCoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to agent-chat

No user-submitted related servers found.

    Related Servers

    • agent-channel-mcp

      MiiKiyoshi
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude and Codex sessions on the same host to communicate across different session systems via shared SQLite rooms, with named participants, durable ordered messages, offline delivery, and wait-based message handling.
      4
      2
      -

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

    • set-agent-comm

      tatargabor
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local agent-to-agent messaging between Claude Code sessions via file-based channels, with a registry, MCP tools and CLI for sending, reading, and tracking messages.
      2
      MIT

    • Agent Wire

      kevinmanase
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents such as Codex and Claude Code to exchange durable, locally stored messages through shared MCP tools for listing enrolled recipients, sending and replying to messages, reading pending inbox items, acknowledging receipt, and checking message status. Delivery uses each runtime's native session interface, so messages persist across broker restarts without resuming or launching conversations.
      AGPL 3.0
    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

    B3.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    post_message, list_messages, and list_rooms have clearly distinct purposes. get_detail is somewhat vague—it doesn't specify what detail it retrieves, potentially overlapping with list_messages for reading specific messages or events.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (post_message, list_messages, list_rooms, get_detail).

    Tool Count4/5

    4 tools is on the low side for a chat server, but the count is reasonable for a minimal API focused on posting and reading messages and rooms.

    Completeness3/5

    Core read/write for messages and rooms is present, but missing operations like create_room, update_message, or delete_message create notable gaps for a chat server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources