mcp-broker
Related Servers
Alternatives to mcp-broker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceA localhost broker that allows multiple MCP clients to share a persistent xcrun mcpbridge connection to Xcode, enabling tool discovery and serialized calls.1MIT
- AlicenseNot gradedqualityBmaintenanceSelf-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.17MIT
- 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.348 npm4MIT
- 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-
- AlicenseAqualityAmaintenanceLocal-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.9345MIT
- AlicenseNot gradedqualityCmaintenanceCentralized MCP control plane that proxies multiple upstream MCP servers with tool namespacing, filtering, policy enforcement, audit logging, and health checks.6 npmMIT
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.