MCP Environment Proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ENV_PROXY_CONFIG | No | Path to the contexts.yaml configuration file. If not set, the server will look in default locations: ./contexts.yaml or ~/.config/mcp-env-proxy/contexts.yaml |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_contextsA | List all available contexts. Returns a list of contexts with their configuration, showing which is currently active and which have cached tools. |
| switch_contextA | Switch to a different context. This changes the active MCP server connection to use different environment variables (AWS_PROFILE, AWS_REGION, etc.). Args: context_name: Name of the context to switch to Returns: Information about the new active context including available tools |
| get_current_contextA | Get information about the current context. Returns: Current context info including available tools |
| proxy_toolA | Call a tool on the current context's MCP server. This forwards the tool call to the underlying MCP server (EKS, ECS, CloudWatch, etc.) with the current context's environment variables. Args: tool_name: Name of the tool to call on the proxied server arguments: Arguments to pass to the tool Returns: Result from the proxied tool |
| list_proxied_toolsA | List tools available from the current context's MCP server. Returns: List of tools with their names and descriptions |
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 distinct and clear purpose: getting current context, listing contexts, listing proxied tools, calling a proxied tool, and switching contexts. There is no overlap.
All tool names use a consistent verb_noun pattern in snake_case (e.g., get_current_context, list_contexts), with clear and predictable naming.
Five tools is appropriate for a proxy server that manages contexts and proxies tool calls; each tool serves a necessary role without redundancy.
The tool set covers the full lifecycle: switching contexts, viewing context info, listing available tools, and executing proxied calls. There are no obvious gaps for the stated domain.