Skip to main content
Glama

Related Servers

Alternatives to mcp-broker

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A localhost broker that allows multiple MCP clients to share a persistent xcrun mcpbridge connection to Xcode, enabling tool discovery and serialized calls.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.
      17
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP auth wrapper and credential broker for multi-account workflows, enabling profile switching, secret injection, and policy enforcement for upstream MCP servers.
      348 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Runs multiple upstream MCP servers behind one local process, keeping sessions persistent and exposing a compact, policy-aware surface for tools, resources, and prompts via HTTP, CLI, and MCP-native clients.
      5
      -
    • A
      license
      A
      quality
      A
      maintenance
      Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.
      9
      345
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Centralized MCP control plane that proxies multiple upstream MCP servers with tool namespacing, filtering, policy enforcement, audit logging, and health checks.
      6 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool occupies a distinct role in the broker workflow: status, search, describe, call, and session cleanup. There is no meaningful overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the broker_ prefix and mostly follow a verb_noun pattern: broker_search_tools, broker_describe_tool, broker_call_tool, broker_close_session. broker_status deviates slightly since it reads as a noun rather than verb_noun, but the naming remains clear and predictable.

    Tool Count5/5

    Five tools is an appropriate size for a broker gateway server. Each tool covers a necessary step in the broker interaction lifecycle without unnecessary bloat.

    Completeness5/5

    The server covers the full broker workflow: check status, search for tools, inspect a tool, call it, and close the session. No essential operation appears missing for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive