Compatible with every major AI agent and IDE
What is the Apache APISIX MCP Server?
Connect your Apache APISIX instance to any AI agent to orchestrate high-performance traffic management through natural language.
What you can do
- Route Orchestration — List, inspect, create, or delete routes to match client requests and forward them to target upstreams.
- Service Abstraction — Manage service entities that group common plugins and upstream configurations for easier API maintenance.
- Upstream Management — Configure virtual host abstractions for load balancing, including node management and health checks.
- Consumer Control — List and manage API consumers to handle authentication and per-user rate limiting.
- Configuration as Conversation — Update complex JSON configurations for any gateway resource without manually using CURL or the Dashboard.
How it works
- Subscribe to this server
- Provide your APISIX Admin URL and Admin Key (X-API-KEY)
- Start managing your microservices infrastructure from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — quickly audit routing rules and upstream health directly from the terminal or chat.
- Backend Developers — create and test new API routes and service abstractions without leaving the IDE.
- SRE Teams — troubleshoot traffic flow and consumer access issues using natural language queries.
Built-in capabilities (50)
Delete an APISIX Consumer
Delete an APISIX Consumer Group
Delete an APISIX Global Rule
Delete an APISIX Plugin Config
Delete an APISIX Proto
Delete an APISIX Route
Delete an APISIX Service
Delete an APISIX SSL certificate
Delete an APISIX Stream Route
Delete an APISIX Upstream
Memory dump of discovered service endpoints
Dump all plugin metadata from the Control API
Dump all configured Routes from the Control API
Dump all configured Services from the Control API
Dump all configured Upstreams from the Control API
Get a specific APISIX Consumer by username
Get a specific APISIX Consumer Group by ID
Get health status of all upstream nodes
Get health status for a specific resource
Get JSON schemas for all resources and enabled plugins
Get a specific APISIX Global Rule by ID
Get a specific APISIX Plugin Config by ID
Get a specific APISIX Proto by ID
Get a specific APISIX Route by ID
Get a specific APISIX Service by ID
Get a specific APISIX SSL certificate by ID
Get a specific APISIX Stream Route by ID
Get a specific APISIX Upstream by ID
List APISIX Consumer Groups
List APISIX Consumers
List APISIX Global Rules
List APISIX Plugin Configs
List APISIX Protos (Protocol Buffers)
List APISIX Routes
List APISIX Services
List APISIX SSL certificates
List APISIX Stream Routes (L4 routing)
List APISIX Upstreams
Create or update an APISIX Consumer
Create or update an APISIX Consumer Group
Create or update an APISIX Global Rule
Create or update an APISIX Plugin Config
Create or update an APISIX Proto
Create or update an APISIX Route
Create or update an APISIX Service
Create or update an APISIX SSL certificate
Create or update an APISIX Stream Route
Create or update an APISIX Upstream
Trigger a hot reload of plugins
Trigger full garbage collection in the HTTP Lua VM
Why LlamaIndex?
LlamaIndex agents combine Apache APISIX tool responses with indexed documents for comprehensive, grounded answers. Connect 50 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Apache APISIX tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Apache APISIX tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Apache APISIX, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Apache APISIX tools were called, what data was returned, and how it influenced the final answer
Apache APISIX in LlamaIndex
Apache APISIX and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Apache APISIX to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Apache APISIX in LlamaIndex
The Apache APISIX MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 50 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Apache APISIX for LlamaIndex
Every tool call from LlamaIndex to the Apache APISIX MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I update a route's configuration directly through the AI?
Yes. Use the put_route tool by providing the Route ID and the new configuration JSON. The agent will interface with the APISIX Admin API to apply the changes immediately.
How do I list all the backend upstreams configured in my gateway?
Simply ask the agent to 'list upstreams'. It will trigger the list_upstreams tool and return a detailed list of all virtual hosts and load balancer nodes.
Is it possible to delete a service that is no longer needed?
Yes, you can use the delete_service tool. Provide the specific Service ID, and the agent will remove the resource from your APISIX configuration.
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Apache APISIX tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
Shippify
11 toolsAutomate logistics and last-mile delivery via Shippify — manage deliveries, tracking, and warehouses directly from any AI agent.

Azure Functions Invoke
1 toolsThis MCP does exactly one thing: it invokes a single Azure Function. That's its only function, and nothing else. Incredible for letting your AI execute secure serverless compute.

Sift (Chargeback)
8 toolsManage fraud prevention and chargebacks via Sift — track user scores, report disputes, and apply decisions directly from any AI agent.

WordPress Post Drafter
1 toolsThis MCP does exactly one thing: it takes content generated by the AI and saves it directly to your WordPress as a Draft. Incredible for turning Claude into an automated SEO content engine.
