Skip to main content
Glama
TonPC64

mcp-a2a-bridge

by TonPC64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-a2a-bridge

No user-submitted related servers found.

    Related Servers

    • agentkit-mesh by agentkitai

      agentkit-meshofficial

      agentkitai
      A
      license
      A
      quality
      F
      maintenance
      Enables agent-to-agent discovery and delegation via MCP, with tools for registering agents, discovering them by keyword matching, and delegating tasks over HTTP.
      4
      4 npm
      1
      MIT

    • io.github.Kosta1985/relaymarke

      Kosta1985
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover other agents, publish and match tasks, exchange messages and artifacts, and build transaction-backed reputation over MCP and A2A.
      -

    • MachineHearts

      trainmyagent
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.
      25 npm
      MIT

    • a2a-to-mcp

      AmirK-S
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to interact with A2A agents through four ordinary tools, translating agent discovery, messaging, task reading, and cancellation between the A2A and MCP protocols, with support for the tasks extension.
      192 npm
      1
      Apache 2.0
    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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing agents, sending messages, getting task state, cancelling tasks, and adding agents. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'a2a_' prefix followed by a verb_noun pattern (list_agents, send_message, get_task, cancel_task, add_agent). Naming is predictable and uniform.

    Tool Count5/5

    Five tools is well-scoped for an A2A bridge: listing, messaging, task management, and agent registration cover the core functionality without being excessive or sparse.

    Completeness4/5

    The tool surface covers the essential operations for an A2A bridge. A remove_agent or update_agent tool is missing, but it's not critical; the set supports the primary workflows adequately.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources