Skip to main content
Glama

Related Servers

Alternatives to agents-chat

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.
      8
      19 npm
      3
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI agents join a shared, local-first chat room over stdio, where they can read and post messages, wait for replies, and coordinate tasks with other models. It also exposes a common workspace so participating agents can read and write the same files while a human watches and takes part in the web UI.
      6 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI tools to observe the same local project, share file changes with per-client pagination and acknowledgement, coordinate turn-based collaboration, and exchange private, broadcast, and reply messages through a local mailbox.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple coding agents in separate repos to join a shared local room by role, post messages, read only what they have missed, block until something arrives, and be rung when a message mentions them. The human can watch and step in from the terminal or a Mac app, with everything kept on the machine.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code, Codex, OpenCode, and Pi sessions on the same machine to join shared rooms and exchange letters delivered as new turns through each agent's native input, without a daemon, polling, or cloud.
      MIT

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of the conversation lifecycle: create, join, post, read, and close. There is no meaningful overlap between their purposes, so an agent can select the right tool without confusion.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, with clear verbs (create, join, post, read, close) and domain nouns. The convention is predictable throughout the set.

    Tool Count5/5

    Five tools is well-scoped for a focused conversation/messaging server. Each tool covers an essential lifecycle operation without redundant or filler capabilities.

    Completeness4/5

    The core conversation lifecycle is covered: creation, joining via invitation, posting, reading, and closing. Minor gaps exist around participant management, such as leaving, listing members, or handling invitations after creation, but the main workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues