Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
One OpenAI-compatible API in front of every model. Route, govern, secure, cache, and observe all your LLM and AI-agent traffic from a single control point β shipped as one static binary with low per-request overhead. Run it in your infrastructure for free, forever.
Built by the original creators of Apache APISIX.
Start free Β· Documentation Β· Quickstart Β· AISIX Cloud Β· Roadmap
AISIX AI Gateway is a Rust-native gateway that puts a single, OpenAI-compatible API in front of every LLM provider β OpenAI, Anthropic, Google Gemini, AWS Bedrock, Azure OpenAI, DeepSeek, and any OpenAI-compatible endpoint. It gives platform teams one place to route, govern, secure, and observe LLM traffic, with first-class SSE streaming and low gateway overhead.
It runs as a single static binary β low cold-start, lock-free config reads, and hot
configuration reloads with no restarts: declare resources in one resources.yaml and
reload on SIGHUP, or point the gateway at etcd for a multi-replica cluster. Run the
open-source gateway in your infrastructure, or connect it to
AISIX Cloud
for centralized management with team governance, budgets, audit, and a dashboard.
AISIX AI Gateway (this repo) is the open-source product. It runs without a control plane using declarative configuration or etcd. When connected to AISIX Cloud, the same gateway serves as the data plane. AISIX Cloud adds a commercial control plane, either hosted by API7 (Hybrid Cloud) or hosted by you in your infrastructure (On-Premises). In both options, the gateway runs in your environment and calls providers directly; live AI traffic does not pass through the control plane or API7. The proxy API is identical throughout. Talk to us about AISIX Cloud β
One container. No control plane, no database, no configuration store β the gateway reads
every dynamic resource from one declarative resources.yaml.
Then call the gateway exactly like OpenAI:
Edit resources.yaml and send SIGHUP (docker kill -s HUP aisix) to apply changes with
no restart β an invalid file is rejected whole and the last good configuration keeps
serving. Check a file before booting with aisix validate --resources resources.yaml.
Full walkthrough: the
Gateway Quickstart Β·
every field: the resources file reference.
For a multi-replica cluster, point the gateway at etcd instead β resources_file and
etcd are mutually exclusive.
base_url and switch models without changing code.Covered by 183 end-to-end scenario files (496 cases) that run against real gateway processes.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/aisix-ai-gateway)<a href="https://allmcps.com/mcp/aisix-ai-gateway"><img src="https://allmcps.com/api/badge/aisix-ai-gateway?style=directory" alt="AISIX AI Gateway on AllMCPs" /></a>