AISIX AI Gateway
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
AISIX MCP gateway: aggregates tools from registered upstream MCP servers, namespaced as server__tool.
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 |
|---|---|
| echo__echoA | Echo the input text back. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly distinct by default.
The name 'echo__echo' follows a namespace-style pattern, but with only one tool there is no broader pattern to evaluate. The double underscore is unusual but not inconsistent within the set.
A single echo tool is extremely thin for a server named 'AI Gateway'. The tool count is far below what the domain implies, making the server feel more like a stub than a functional gateway.
The tool surface is severely incomplete for any plausible interpretation of an AI Gateway. It lacks any gateway-related operations such as routing, request handling, model access, or configuration.