proxy-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_mcp_toolA | Execute any available MCP tool through the proxy. This is the universal gateway for calling MCP tools. The proxy spawns MCP servers on-demand and maintains a connection pool for efficient reuse. MCP configurations are read from ~/.claude.json or ~/.agentcockpit/mcps.json. |
| search_toolsA | Search tools by objective or description using semantic similarity. Useful when you don't know the exact tool name but know what you want to do. |
| list_available_mcpsA | List all configured MCP servers and their connection status. Returns the names of all MCP servers found in configuration, along with which ones have active connections. |
| get_learned_weightsA | View the learned weights from the search system. Shows which tools have been selected and for which keywords, revealing how the system has learned from your selections. |
| reset_learned_weightsA | Reset all learned weights. WARNING: This erases all accumulated learning. |
| refresh_tool_indexA | Refresh the tool index for semantic search. Connects to MCP servers and retrieves their tool lists for indexing. Use after adding new MCPs. The index is auto-loaded on server startup. |
| close_mcp_connectionsA | Close all active MCP connections. Use this to clean up resources when done with MCP tools. Connections will be re-established on next use. |
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 7 tools
Each tool has a clearly distinct purpose: execution, search, server listing, weight management, index refresh, and connection cleanup. There is no functional overlap between any pair of tools.
All tool names follow a uniform verb-first snake_case pattern (e.g., execute_mcp_tool, list_available_mcps, reset_learned_weights). The verbs are action-oriented and consistently describe the operation.
Seven tools is well-scoped for a proxy MCP server covering discovery, execution, learning, and maintenance. Each tool earns its place without redundancy or bloat.
The tool set covers all essential operations for the proxy's purpose: finding tools (search_tools, refresh_tool_index), executing tools (execute_mcp_tool), managing servers (list_available_mcps, close_mcp_connections), and controlling learning (get/reset_learned_weights). No significant gaps are evident.