@mhdd_24/ai-gateway-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_GATEWAY_URL | Yes | The URL of the AI gateway | |
| AI_GATEWAY_TOKEN | Yes | The token for authenticating with the AI gateway |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aigw_statusC | Show manage multiple llm providers configuration / health. |
| aigw_listC | List manage multiple llm providers entities. |
| aigw_inspectC | Inspect a manage multiple llm providers artifact. |
| aigw_compareD | Compare two manage multiple llm providers items. |
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
The four tools are mostly distinct: status reports health/configuration, list enumerates entities, inspect drills into one artifact, and compare contrasts two items. There is mild potential overlap between status and inspect, but descriptions are clear enough for an agent to select the intended operation.
All tool names follow the same aigw_<verb> pattern using simple, consistent verbs. This creates a predictable convention across the entire tool set.
Four tools is a reasonable, focused count for a read-only gateway observability utility. It sits slightly low for a server claiming to 'manage' providers, but the count itself is not excessive or trivial.
The tool surface only supports reading and comparing gateway entities; there are no create, update, delete, or configuration-change operations. Given the 'manage' framing, this is a significant functional gap that would prevent agents from actually managing providers.