mcp-broker
Related Servers
Alternatives to mcp-broker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA localhost broker that allows multiple MCP clients to share a persistent xcrun mcpbridge connection to Xcode, enabling tool discovery and serialized calls.1MIT
- AlicenseNot gradedqualityCmaintenanceFronts many downstream MCP servers through one session, presenting a unified tool namespace with collision resolution, fleet-wide allow/deny/hide policy, per-tool rate limits, centralized audit logging, Prometheus metrics, and bearer-key auth at the edge. Supports both stdio drop-in and Streamable HTTP deployment so agents point at a single endpoint instead of N servers.MIT
- AlicenseNot gradedqualityCmaintenanceSelf-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.18MIT
- AlicenseNot gradedqualityCmaintenancePresents multiple stdio backend tool servers to an MCP client as one aggregated server, sharing those backend processes across concurrent agent sessions through a background broker while namespacing and routing each tool call to the right backend. Servers can be run shared, per-session, or lazily, with automatic restart and request ID remapping so many sessions coexist without collisions.MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP auth wrapper and credential broker for multi-account workflows, enabling profile switching, secret injection, and policy enforcement for upstream MCP servers.18 npm5MIT
- FlicenseNot gradedqualityAmaintenanceRuns 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-
TDQS
Scored across 5 tools
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.
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.
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.
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.