Management Options
APISIX provides several management options for routes, upstreams, plugins, and other gateway resources. Each option supports a different way to describe, review, and apply changes.
The Getting Started tutorials show Admin API, ADC, and APISIX-MCP examples side by side. The APISIX agent skills use a6 to manage APISIX resources.
| Option | How it works | Common operational scenarios |
|---|---|---|
| Admin API | Provides RESTful endpoints for individual resource operations. | Custom controllers, internal platforms, and applications that need fine-grained integration with APISIX. |
| API Declarative CLI (ADC) | Applies declarative YAML or JSON configuration from a separately installed CLI. | GitOps and CI/CD workflows where files are the source of truth, including linting, validation, drift review, environment promotion, and approved synchronization. |
| a6 CLI | Runs resource and diagnostic commands against the Admin API from a separately installed CLI. | Terminal operations, scripts, and AI coding agents that support Agent Skills and shell commands. |
| APISIX-MCP | Exposes APISIX operations as tools through a separately configured MCP server. | AI clients and agents that support MCP and need resource operations or gateway test requests. |
ADC, a6, and APISIX-MCP are not bundled with APISIX. Set up ADC or APISIX-MCP before following the examples for that option. If you use the APISIX agent skills, install a6 first.
Use APISIX with an AI Agent
Both a6 and APISIX-MCP can connect an AI agent to APISIX, but they work differently. The APISIX agent skills provide APISIX-specific instructions and examples, which a shell-capable coding agent follows by running a6 commands. APISIX-MCP provides structured tools that an MCP-compatible client or agent can discover and call.
You do not need both for the same task. Use the a6 skills when your agent supports Agent Skills and shell commands. Use APISIX-MCP when your client or agent supports MCP and you want to expose APISIX operations through an MCP server.
What's Next
You have now reviewed the available management options. Next, configure your first route using the option that fits your workflow.