MCP Bridge Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_clientC | Find and optionally start an MCP client |
| tools/callC | Execute a tool on a remote MCP client |
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 2 tools
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.
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.
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.
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.