mcp-proxy
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversA | List all proxied MCP servers available in this proxy. |
| list_toolsA | List tools available on a server. Returns names and short descriptions only (low token cost). Use read_tool to get the full schema before calling. |
| read_toolC | Read the full input schema for a specific tool on a server. |
| call_toolB | Execute a tool on a proxied MCP server. |
| refresh_cacheB | Force re-fetch tool definitions from a server (or all servers) and update cache. |
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 has a clear, distinct purpose: listing servers, listing/reading tools, calling tools, and cache refresh. There is no overlap or ambiguity.
All tools use snake_case and follow a consistent verb_noun pattern (e.g., call_tool, list_servers). No deviations.
5 tools cover the core proxy functionality. While minimal, it's reasonable for a proxy that relies on downstream servers. Could be expanded slightly for server management.
Core operations (listing servers, tools, calling, cache refresh) are present. Missing server add/remove or configuration, but the set is mostly complete for basic use.