DynamicMCPProxy
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxy_handshakeA | Send your project context to the proxy. It will activate the most relevant MCP servers from the catalogue and return a summary of available tools. Args: tech_stack: Languages and frameworks in use, e.g. ["python", "fastapi", "postgres"] task_description: Free-text description of what you are working on open_files: File paths currently open in the IDE (optional, helps infer stack) requirements: Package names from requirements.txt / package.json (optional) |
| proxy_list_active_serversA | List all currently mounted MCP servers and their estimated tool counts. |
| proxy_list_available_serversA | List MCP servers in the catalogue that are not yet mounted. Args: filter_tag: Optional tag filter, or free-text query (uses search_servers for discovery). |
| proxy_search_toolsA | Search the catalogue for relevant servers/tools using free-text query. Enables on-demand discovery (lazy loading pattern) so the AI can find specific capabilities without the full catalogue bloating context. Returns ranked list of matching servers (name, desc, score, tags). Use proxy_activate_server on results, or let handshake do it. Inspired by MCP tool search / lazy discovery best practices (Anthropic, Stacklok, etc.). |
| proxy_list_toolsA | List all registered tools by inspecting the FastMCP instance. If server_name is provided, filters for tools from that child server. |
| proxy_inspect_registryB | Diagnostic tool: Expose proxy state and server counts. |
| proxy_activate_from_specA | Generate an MCP server from an OpenAPI/GraphQL spec and activate it. Args: name: A unique name for this generated server spec_url: URL to the OpenAPI spec (JSON/YAML) or GraphQL endpoint spec_type: 'openapi' or 'graphql' eager: If True, mount the server immediately lean: If True, attempt to use LAP (https://lap.sh) to produce a dramatically leaner input spec before 40mcp generation (F-12 research slice). Falls back gracefully if LAP CLI not available. |
| proxy_activate_serverA | Activate (mount) a server from the catalogue by name. By default the server is registered as a deferred stub ( Args: name: Server name as shown in proxy.list_available_servers() eager: If True, spawn the subprocess immediately instead of deferring. |
| proxy_deactivate_serverA | Deactivate (unmount) a currently loaded or pending server to free up tool budget. Args: name: Server name as shown in proxy.list_active_servers() |
| proxy_add_custom_proxyA | Register a custom (non-catalogue) MCP server and optionally activate it. Only SSE and HTTP runtimes are accepted; stdio is restricted to prevent arbitrary command execution. Args: name: A unique identifier for this server url: SSE URL (e.g. http://localhost:8100/sse) or HTTP URL tags: Tag list for future discovery matching runtime: "sse" or "http" (stdio is not permitted for custom proxies) activate_now: If True, mount the server immediately |
| proxy_get_metricsA | Return live process metrics for the proxy itself. Mirrors the mcp://proxy/health resource as a callable tool. |
| proxy_get_usageB | Return current server usage counts for self-evolving ranking (F-13). |
| proxy_reset_usageA | Reset usage stats (all or for one server). Useful for testing or re-baselining. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| suggest_tools_for_context | Guided workflow: describe your project context and let the proxy suggest and activate the most relevant MCP tool servers. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_info | Static proxy metadata: name, version, protocol, capabilities. |
| resource_health | Live process health: uptime, memory, CPU time, thread count. |
| resource_servers | Aggregated child server inventory with tool counts and status. |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: handshake, listing servers, searching, activation/deactivation, spec generation, metrics, usage tracking, etc. No two tools appear to overlap in functionality.
All tools follow the 'proxy_verb_noun' pattern with consistent snake_case. Verbs like 'list', 'activate', 'get', 'reset' are used uniformly, making the naming predictable.
13 tools is well-scoped for a proxy management server, covering setup, discovery, activation, inspection, and usage tracking without being overwhelming or too sparse.
The tool surface covers the core workflows (handshake, list, search, activate, deactivate, add custom, metrics, usage). A minor gap is the lack of a tool to get detailed server info (beyond counts), but overall it's quite complete.