Skip to main content
Glama
amyodov

io.github.amyodov/yet-another-agentic-chat

Related Servers

Alternatives to io.github.amyodov/yet-another-agentic-chat

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.
      44 npm
      17
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that enables direct, persistent communication between multiple Claude Code agent sessions through a secure messaging channel. It includes built-in guardrails to manage message exchanges and supports optional human monitoring via Telegram.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
      8
      45 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      123 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents on different machines to communicate and collaborate directly through relay channels, supporting structured agent contracts, real-time messaging, and human-in-the-loop approval workflows.
      9,508 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP central server that lets multiple AI agents (e.g., Claude Code, kimi-code) exchange private messages, shared channel broadcasts, and unified message streams via MCP tools, with SQLite persistence and per-connection identity binding.
      31 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    list_channels and join_channel are completely distinct: one is a read-only observation of available channels, the other is a state-changing action to enter or create a channel. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern with snake_case: list_channels and join_channel. This is clean, predictable, and consistent.

    Tool Count2/5

    For a chat-oriented server, exposing only two tools is far too thin. The join_channel description implies that core messaging tools like send and check_inbox are needed after joining, but they are not part of the exposed tool set, leaving the server's actual surface severely underpowered.

    Completeness1/5

    The tool set has no way to send messages, receive messages, see other participants, or leave a channel after joining. Even though join_channel mentions these capabilities, they are not actual tools in the server, so an agent can join a channel but cannot communicate, making the surface effectively a dead end.

    Maintenance

    ActivityActive
    ResponsivenessNo issues