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
      C
      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.
      73 npm
      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
      20 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      107 npm
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      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.
      3,587 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      49 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct chat action: joining/leaving, sending, reading mail, listing peers, listing channels. The only mild overlap is dev_connections versus peers/list_channels, since a session holding one connection can learn much of the same information from either; the diagnostic framing mostly resolves this.

    Naming Consistency3/5

    Most names follow a verb_noun or noun_plural pattern (join_channel, leave_channel, list_channels, check_inbox), but 'send' is a bare verb with no object and 'peers' is a bare noun, while 'dev_connections' is noun-based with an adjective prefix. Readable, but conventions are mixed.

    Tool Count5/5

    Seven tools is well within the sweet spot and each earns its place: join/leave lifecycle, send, receive, peer listing, channel discovery, and one diagnostic. Nothing feels padded or redundant.

    Completeness4/5

    The surface covers the full chat lifecycle — join, leave, send, receive, discover channels and peers — plus a diagnostic escape hatch for recovering connection state. Minor gaps exist around message history/backlog and per-connection configuration, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues