mcp-broker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| broker_search_toolsA | Search the profile-visible upstream MCP tool catalog without advertising every upstream tool to the client. Use this first when the task mentions a capability, service, keyword, or upstream prefix and you need candidate broker-qualified tool names before describing or calling one of them. |
| broker_describe_toolA | Describe one profile-visible upstream MCP tool by broker-qualified name. Use this after broker_search_tools and before broker_call_tool so the client can inspect the exact description, input schema, upstream owner, transport, and mutating metadata instead of guessing arguments. |
| broker_call_toolA | Call one profile-visible upstream MCP tool through the broker using its broker-qualified name and exact argument object. The broker's mutating-tool policy remains gated by the active profile's allowlist, so call broker_describe_tool first and pass only arguments accepted by the described upstream schema. |
| broker_statusA | Report broker and upstream status for the active profile without starting hidden or denied upstreams. Use this for health checks, support tickets, and client validation because it returns the profile name, broker socket path, aggregate status, upstream runtime state, auth state, transport, process id, restarts, and mutating exposure. |
| broker_close_sessionA | Release the broker-owned per-session upstream processes for the current client session. Use this after shutting down a client session when its session-scoped MCP subprocesses must exit promptly. This never stops shared upstreams or another client's session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.