Skip to main content
Glama
jeffreyjorgensen

ai-agent-channel

by jeffreyjorgensen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ai-agent-channel

No user-submitted related servers found.

    Related Servers

    • MCP Agent Mail

      Dicklesworthstone
      A
      license
      B
      quality
      A
      maintenance
      A coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.
      41
      2,228
      MIT

    • messhall

      maximilianfalco
      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

    • agentsocks

      Aelethion
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code, Codex, and other coding-agent sessions on the same machine to message each other, exchange tracked tasks with owners and states, and coordinate through channels, broadcasts, and multi-session asks without typing into terminals. Messages are routed by what the receiver is doing — next tool call, end of turn, or a held-back digest — so a flood of traffic doesn't interrupt active work.
      14
      MIT

    • Swarmail

      bompus
      A
      license
      A
      quality
      A
      maintenance
      Local agent-to-agent messaging and coordination for coding sessions on one machine, through MCP and a CLI. Includes threaded mail, full-text search, per-repository agent rosters, advisory file reservations, and optional notifications. Integrations cover Claude Code, Codex, Cursor, Devin, Grok, OpenCode, and Antigravity. Standalone agents and T3 Code sessions can share the same local server.
      2
      23
      2
      MIT

    • Placet MCP

      Pablo-gitub
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to ask the user questions, receive written replies, share files, and hand tasks to other agent sessions — with every cross-agent request routed through human approval first. Sessions register themselves so they can be read, woken, and answered from a phone over a local-first, self-hosted setup.
      2
      Apache 2.0
    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

    A4.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and the extensive descriptions help differentiate them. However, there is some potential confusion among list_messages vs search_messages, resolve_message vs confirm_resolution vs reopen_message, and open_obligations vs ready_work vs awaiting_ack.

    Naming Consistency3/5

    All names use snake_case, but the pattern is inconsistent: many are verb_noun (send_message, delete_message, create_channel), while others are noun_action (pin_set, pin_get, pin_history) or noun_noun (message_history, channel_status), and one is verb-only (acknowledge). This mixed convention is still readable but not predictable.

    Tool Count2/5

    At 41 tools, the server is far beyond the typical 3-15 well-scoped range and above the 25+ threshold. While each tool has a distinct purpose, the large surface includes niche utilities (backfill_superseded, undo_backfill, get_charter_template) and 6 admin-only tools, making the set heavy and potentially overwhelming for an agent.

    Completeness4/5

    The tool surface covers the core domain well: messaging lifecycle, obligations, decisions/pins, content upload, role administration, search, and polling. Minor gaps exist, such as no remove_role, no editing of non-proposal messages (only revise for proposals), and addenda only at send time, but these are workable and do not block main workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources