Skip to main content
Glama
parampratap-star

a2a-mcp-bridge

by parampratap-star
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to a2a-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • ejentum-mcp by ejentum

      ejentum-mcpofficial

      ejentum
      A
      license
      A
      quality
      D
      maintenance
      Exposes the four Ejentum cognitive harnesses (reasoning, code, anti-deception, memory) as MCP tools any agentic client can call. Drop-in scaffolding that catches LLM failure modes like sycophancy, hallucination, and reasoning shortcuts.
      4
      40 npm
      16
      MIT

    • small-model-agents

      salimkt
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-aware clients to use a reliable multi-agent tool system with tiered model routing, schema-validated decisions, and graceful tool degradation, allowing small models to handle complex tasks.
      MIT

    • Grok Bot MCP Bridge

      mozzquito
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.
      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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: ask_agent for interaction, get_last_trace for inspecting the latest turn, get_agent_card for metadata, and reset_conversation for state management. There is no overlap between them.

    Naming Consistency5/5

    All tool names follow the same verb_noun snake_case pattern (ask_agent, get_last_trace, get_agent_card, reset_conversation). The style is uniform and predictable.

    Tool Count5/5

    Four tools is a well-scoped set for a single-agent bridge. Each tool covers an essential function without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full lifecycle of interacting with the A2A agent: sending messages, inspecting agent capabilities, reviewing trace details, and resetting conversation state. No obvious dead ends or missing operations for this narrow domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources