Agent MCP Gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATEWAY_DEBUG | No | Enable debug mode to expose get_gateway_status tool | true |
| GATEWAY_RULES | No | Path to gateway rules configuration file | .mcp-gateway-rules.json |
| GATEWAY_MCP_CONFIG | No | Path to MCP servers configuration file | .mcp.json |
| GATEWAY_DEFAULT_AGENT | No | Default agent identity when agent_id not provided | default |
| GATEWAY_INIT_STRATEGY | No | Initialization strategy (eager or lazy) | eager |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_serversA | Discover downstream MCP servers available through this gateway. Your access is determined by gateway policy rules. Workflow: 1) Call list_servers to discover servers, 2) Call get_server_tools to see available tools, 3) Call execute_tool to use them. |
| get_server_toolsA | Discover tools available on a downstream MCP server accessed through this gateway. Returns only tools you have permission to use (filtered by policy rules). Use the returned tool definitions to call execute_tool. |
| execute_toolA | Execute a tool on a downstream MCP server accessed through this gateway. Gateway validates permissions then forwards your request to the server. Returns the server's response directly. |
| get_gateway_statusA | Get gateway status, configuration state, and hot reload diagnostics. NOTE: Only available when debug mode is enabled. |
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 4 tools
Each tool has a distinct purpose: listing servers, discovering tools on a server, executing tools, and checking gateway status. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (execute_tool, get_gateway_status, get_server_tools, list_servers).
With 4 tools covering discovery and execution for a gateway, the count is well-scoped and appropriate for the server's purpose.
The tools provide a complete workflow: list servers, discover tools, and execute them, with an additional status tool. No obvious gaps for a gateway.