Skip to main content
Glama
mgcrea

@mgcrea/mcp-a2a

by mgcrea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @mgcrea/mcp-a2a

No user-submitted related servers found.

    Related Servers

    • slm-mesh

      qualixar
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.
      5 npm
      19
      Elastic 2.0

    • MCPBridge

      DonkRonk17
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables BCH agents to be exposed via MCP/A2A protocols for discovery and task delegation, and allows delegation to external A2A agents.
      MIT

    • zahadun

      medelin
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and OpenCode agents to delegate tasks to peer machines over a self-hosted A2A mesh, using mTLS identity and executing via local CLIs or scripts.
      8
      Apache 2.0

    • a2a-bridge

      joltedbot
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional A2A communication between AI coding agents, allowing Claude Code to reach out to and be reached by other A2A agents via an MCP bridge and an HTTP server.
      3 npm
      MIT

    • claude-intercom-mcp

      dataforxyz
      A
      license
      A
      quality
      B
      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
      9 npm
      2
      AGPL 3.0

    • Esco

      JonusNattapong
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate asynchronously via a decentralized, peer-to-peer LAN bridge with automatic discovery and direct messaging.
      MIT
    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

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly separated purpose: status/setup, agent listing, agent discovery, task listing, task detail, task waiting, and raw protocol fallback. The descriptions explicitly distinguish cache reads from network fetches and summaries from full task bodies, so an agent should not confuse one tool for another.

    Naming Consistency4/5

    All tools share the a2a_ prefix and consistently use lowercase snake_case action-style names. The main deviations are a2a_auth_status, which is more of a noun phrase than a clean verb_noun pair, and a2a_request, which lacks a specific object.

    Tool Count5/5

    Seven tools is a well-scoped size for an A2A server: setup/status, peer discovery, task retrieval/list/waiting, and one raw protocol escape hatch. There is no apparent padding or redundant duplication.

    Completeness3/5

    The set has a notable lifecycle gap: there is no typed send_message or respond_to_task tool, even though several descriptions refer to those operations. The raw a2a_request escape hatch can partially cover them, but it is unshaped and write-disabled by default, making the missing typed tools more than a trivial gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources