AI Gateway MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_GATEWAY_API_KEY | Yes | Vercel AI Gateway API key | |
| ZERO_DATA_RETENTION | No | Set to 'true' to enable Gateway-level Zero Data Retention |
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 |
|---|---|
| askA | Ask a single AI model a question (no web search, cannot retrieve latest/real-time information). Default: openai/gpt-5.4 (flagship, $2.50/$15, 1.05M ctx). For multiple perspectives on a question, prefer research tool with mode:ask synthesize:false. For code: openai/gpt-5.3-codex. For mid-tier: openai/gpt-5.4-mini ($0.75/$4.50, strong reasoning). For cheaper: openai/gpt-5-mini ($0.25/$2) or google/gemini-3.1-flash-lite-preview ($0.25/$1.50). For cheap with coding: openai/gpt-5.4-nano ($0.20/$1.25). For cheapest: openai/gpt-5-nano ($0.05/$0.40). |
| searchA | Web search with a single model. Use for real-time lookups. For multi-model parallel research, use the research tool. Query tips (major accuracy improvement):
Model guide ($ = cheapest, $$$ = most expensive):
For parallel multi-model results or diverse perspectives, use the research tool. |
| researchA | Multi-model parallel research. Queries 2-4 AI models simultaneously, then optionally synthesizes results. Use instead of search when: (1) you need higher confidence via cross-validation across sources, (2) you want diverse perspectives on a topic. mode:search (default): web research with grounding across 3 models (sonar, gemini-3-flash, gpt-5.4-nano). mode:ask: multi-model Q&A without web search — for architecture decisions, trade-off analysis, diverse expert opinions (uses gpt-5.4, claude-opus-4.6, gemini-3.1-pro-preview, sonar-reasoning-pro). synthesize:true (default): merges all responses into one comprehensive answer. synthesize:false: shows each model side-by-side with latency and cost — useful for comparing perspectives or when you want raw answers. Query tip: prefer English for technical topics, one focused topic per query. NEVER include specific years in queries — use "latest"/"current"/"newest" instead. Same best practices as the search tool apply. |
| list_modelsA | List available AI models with capabilities, pricing, and web search costs. Use this to choose the right model for your task. |
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
There is some overlap between search and research (mode:search) and between ask and research (mode:ask), but the descriptions clearly explain the differences (single vs. multi-model, with or without web search). The primary purposes are distinct enough that an agent can reliably select the right tool.
All tool names are lowercase imperative verbs (list_models, ask, search, research), with 'list_models' being the only verb_noun combo. There are no mixed styles like camelCase or inconsistent verb forms, making the naming pattern predictable and clear.
With only four tools, the set is tightly scoped for an AI gateway: listing models, single-query ask, single-query search, and multi-model research. Each tool earns its place and there is no bloat or unnecessary overlap for the stated purpose.
The main operations for an AI gateway are covered—listing models, asking without search, searching with web access, and multi-model research. Minor gaps like streaming responses or detailed model comparison are absent, but they are not essential for typical AI query workflows, so agents can work around them.