Most of the surface is CRUD over the Admin API, which is what makes it useful for bulk edits and for reading a configuration you did not write. The tool that changes the loop is the request sender: create or edit a route, then push traffic through the gateway in the same session and see whether it matched.
A server in front of the APISIX Admin API. It reads and writes the gateway's configuration objects — routes, services, upstreams, SSL certificates, plugins, consumers and secrets — and can fire requests at the gateway itself to see what the configuration actually does.
- Routes, services and upstreams created, updated and deleted, with load-balancing settings on the upstream
- Any resource fetched by ID or listed by type, and deleted by ID
- Plugin names, schemas and metadata read back, and plugin configs and global rules written
- Consumers, consumer groups and their credentials managed together
- SSL certificates, secrets, stream routes and protobuf definitions created and updated
- A request — or a batch of them — sent through the gateway to check the result
A reachable APISIX instance and its Admin API key. Host and Admin API details are supplied as environment settings. Runs under Node from the published package, or from a build of the repository.
One command — npx -y apisix-mcp