Skip to main content
Glama
glassBead-tc

MCP Bridge Server

by glassBead-tc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to MCP Bridge Server

No user-submitted related servers found.

    Related Servers

    • ACP-MCP-Server

      GongRzhe
      A
      license
      B
      quality
      F
      maintenance
      A bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.
      16
      24
      MIT

    • ChatGPT MCP Server

      xncbf
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that allows AI assistants to communicate with the ChatGPT desktop app on macOS, enabling users to send prompts to ChatGPT from any MCP-compatible assistant.
      3
      77
      MIT

    • PAL MCP

      ramarivera
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.
      -

    • Claude IPC MCP

      jdez427
      A
      license
      B
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to communicate with each other using Inter-Process Communication, featuring natural language commands and cross-platform compatibility.
      9
      133
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: discover_client is for finding/starting clients, while tools/call is for executing tools on those clients. There is no overlap or ambiguity between these functions, making them easy to differentiate.

    Naming Consistency3/5

    The naming is mixed: discover_client uses snake_case with a verb-noun pattern, while tools/call uses a path-like structure (noun/verb). This inconsistency in convention reduces predictability, though both names are still readable and descriptive.

    Tool Count4/5

    With only 2 tools, the count is minimal but appropriate for a bridge server's core functions of discovering clients and calling their tools. It feels slightly thin but covers essential operations without unnecessary bloat.

    Completeness4/5

    For a bridge server, the tools cover the key workflows: discovering clients and executing tools on them. A minor gap might be the lack of a tool for managing client connections (e.g., disconnecting), but the core functionality is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources