Apisix MCP logo

Apisix MCP

by api7

Manage Apache APISIX routes, services, plugins, security resources, and gateway requests through MCP-compatible AI clients.

Install Apisix MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "api7-apisix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "apisix-mcp"
      ],
      "env": {
        "APISIX_SERVER_HOST": "YOUR_VALUE_HERE",
        "APISIX_SERVER_PORT": "YOUR_VALUE_HERE",
        "APISIX_ADMIN_API_PORT": "YOUR_VALUE_HERE",
        "APISIX_ADMIN_API_PREFIX": "YOUR_VALUE_HERE",
        "APISIX_ADMIN_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 32 tools correctly (1mo ago).

Overview

The api7/apisix-mcp MCP server connects MCP-compatible AI clients to the Apache APISIX Admin API. It exposes tools for reading and changing routes, services, upstreams, SSL certificates, plugins, consumers, credentials, and other APISIX resources, plus sending requests to the gateway. Configuration uses environment variables for the APISIX host, ports, Admin API prefix, and authentication key. Reach for it when an agent needs to inspect or manage an existing APISIX deployment through natural-language interactions.

Use cases

  • Inspect APISIX routes and upstreams through an AI client
  • Create or update gateway routes using natural-language requests
  • Review plugin schemas and available plugin names
  • Manage APISIX consumers, credentials, and secrets
  • Send test requests to the APISIX gateway

Key features

  • Manage routes, services, upstreams, and SSL certificates
  • Inspect and configure APISIX plugins
  • Manage consumers, credentials, secrets, and groups
  • Create protobuf definitions and stream routes
  • Send single or multiple gateway requests
  • Access APISIX through the Admin API

Tools32

What Apisix MCP lets your agent do. Expand a tool for its parameters.

Verified live~15.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

17/17 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · apisix-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars38Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed32Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Apisix MCP works

What the api7/apisix-mcp MCP server does

The api7/apisix-mcp MCP server bridges MCP-compatible AI clients with Apache APISIX. It uses the APISIX Admin API to let an agent inspect gateway resources, modify configurations, and send requests to the APISIX gateway. APISIX must already be installed and running before this server can provide useful operations.

Supported resource areas include routes, services, upstreams, SSL certificates, protobuf definitions, stream routes, plugin configurations, global plugin rules, plugin metadata, secrets, consumers, consumer credentials, and consumer groups. The server also provides general resource retrieval and deletion operations, along with a way to send one or more requests to the gateway.

How it works

An MCP client starts the server locally, and the server communicates with the configured APISIX instance through its Admin API. The client supplies tool calls based on the agent's request; those calls map to operations such as creating a route, updating an upstream, retrieving plugin information, or deleting a consumer.

The api7/apisix-mcp MCP server includes separate operations for creating, updating, and deleting several APISIX resource types. Plugin-related tools can list available plugin names, return plugin information or schemas, and manage plugin configurations, global rules, and metadata. Security-focused tools cover secrets, consumers, credentials, and consumer groups.

Setup and configuration

First set up and run APISIX using the project's getting-started guidance. When using the published npm package, configure the MCP client to launch npx with -y apisix-mcp. A source-based setup instead clones the repository, runs pnpm install, builds with pnpm build, and launches the resulting dist/index.js with Node.

Configuration is supplied through environment variables:

  • APISIX_SERVER_HOST identifies the host that can access APISIX; the documented default is http://127.0.0.1.
  • APISIX_SERVER_PORT sets the APISIX server port; the documented default is 9080.
  • APISIX_ADMIN_API_PORT sets the Admin API port; the documented default is 9180.
  • APISIX_ADMIN_API_PREFIX sets the Admin API path prefix; the documented default is /apisix/admin.
  • APISIX_ADMIN_KEY provides the Admin API authentication key.

The client examples mention Claude Desktop, Cursor, and Copilot configurations. The server needs network access to the APISIX host and valid Admin API authentication.

Tools and capabilities

The api7/apisix-mcp MCP server supports these capability groups:

  • Retrieve resources by type and delete resources by ID.
  • Create, update, and delete routes, services, upstreams, and SSL certificates.
  • Create or update protobuf definitions and stream routes.
  • Inspect plugin names, information, types, schemas, and metadata.
  • Create or update plugin configurations and global rules.
  • Manage secrets, consumers, credentials, and consumer groups.
  • Send a single request or multiple requests to the APISIX gateway.

The exact resource fields and Admin API behavior remain governed by the APISIX version and its Admin API documentation.

Limitations and notes

This project manages APISIX through the Admin API; it is not an APISIX installation or gateway replacement. Because the available operations can change gateway state and security configuration, the configured Admin API key should have appropriate access for the intended environment.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Apisix MCP

Configure the client to run `npx -y apisix-mcp`, or clone the repository, install dependencies with `pnpm install`, build with `pnpm build`, and run the generated `dist/index.js`.

Yes. The README provides a Claude Desktop configuration and documents installation through Smithery for Claude.

It documents `APISIX_SERVER_HOST`, `APISIX_SERVER_PORT`, `APISIX_ADMIN_API_PORT`, `APISIX_ADMIN_API_PREFIX`, and `APISIX_ADMIN_KEY` for APISIX connection and Admin API authentication.

Yes. It can list plugin names, retrieve plugin information and schemas, manage plugin configurations and global rules, and manage plugin metadata.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewApisix MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/api7-apisix-mcp?style=directory)](https://allmcps.com/mcp/api7-apisix-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/api7-apisix-mcp"><img src="https://allmcps.com/api/badge/api7-apisix-mcp?style=directory" alt="Apisix MCP on AllMCPs" /></a>