mcp-api-gateway
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_1_NAME | Yes | Unique API name (e.g., my-api) | |
| API_1_TAGS | No | Comma-separated OpenAPI tags to include | |
| API_1_HEADERS | No | JSON object with multiple headers | |
| API_1_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| API_1_BASE_URL | No | API base URL (overrides spec) | |
| API_1_TOOL_MODE | No | Tool mode: 'individual' or 'grouped' | individual |
| API_1_MAX_RETRIES | No | Max retry attempts for 429/5xx errors | 3 |
| API_1_PATH_PREFIX | No | Comma-separated path prefixes to include | |
| API_1_SCHEMA_MODE | No | Schema mode: 'full' or 'compact' | full |
| API_1_SWAGGER_URL | Yes | Swagger/OpenAPI spec URL | |
| MAX_RESPONSE_SIZE | No | Max response size in bytes before truncation | 102400 |
| API_1_EXCLUDE_PARAMS | No | Comma-separated parameter names to strip | |
| API_1_HEADER_AUTHORIZATION | No | Authorization header value |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_api_infoA | Get information about available APIs and their endpoints |
| check_api_healthB | Check connectivity and health of configured APIs |
| execute_apiC | Execute any API endpoint with custom parameters |
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 3 tools
Each tool has a clear, distinct purpose: get_api_info retrieves metadata, check_api_health tests connectivity, and execute_api performs API calls. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (get_api_info, check_api_health, execute_api) using snake_case. The naming is uniform and predictable.
Three tools is an appropriate scope for an API gateway server, covering information retrieval, health checking, and execution without being excessive or insufficient.
The tools cover the core functions of an API gateway: discovery, health, and execution. Minor gaps like authentication management or rate limiting are missing but not critical for basic use.