Apache APISIX MCP Server for Claude DesktopGive Claude Desktop instant access to 50 tools to Delete Consumer, Delete Consumer Group, Delete Global Rule, and more

Name: Apache APISIX
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

Open in ChatGPT Open in Claude Open in Perplexity

The Apache APISIX MCP Server for Claude Desktop is a standout in the Loved By Devs category — giving your AI agent 50 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "apache-apisix": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Apache APISIX and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Apache APISIX MCP Server

Connect your Apache APISIX instance to any AI agent to orchestrate high-performance traffic management through natural language.

Claude Desktop is the definitive way to connect Apache APISIX to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 50 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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.

The Apache APISIX MCP Server exposes 50 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 50 Apache APISIX tools available for Claude Desktop

When Claude Desktop connects to Apache APISIX through Vinkius, your AI agent gets direct access to every tool listed below — spanning api-gateway, traffic-management, cloud-native, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

delete

Delete consumer on Apache APISIX

Delete an APISIX Consumer

delete

Delete consumer group on Apache APISIX

Delete an APISIX Consumer Group

delete

Delete global rule on Apache APISIX

Delete an APISIX Global Rule

delete

Delete plugin config on Apache APISIX

Delete an APISIX Plugin Config

delete

Delete proto on Apache APISIX

Delete an APISIX Proto

delete

Delete route on Apache APISIX

Delete an APISIX Route

delete

Delete service on Apache APISIX

Delete an APISIX Service

delete

Delete ssl on Apache APISIX

Delete an APISIX SSL certificate

delete

Delete stream route on Apache APISIX

Delete an APISIX Stream Route

delete

Delete upstream on Apache APISIX

Delete an APISIX Upstream

dump

Dump control discovery on Apache APISIX

Memory dump of discovered service endpoints

dump

Dump control plugin metadatas on Apache APISIX

Dump all plugin metadata from the Control API

dump

Dump control routes on Apache APISIX

Dump all configured Routes from the Control API

dump

Dump control services on Apache APISIX

Dump all configured Services from the Control API

dump

Dump control upstreams on Apache APISIX

Dump all configured Upstreams from the Control API

get

Get consumer on Apache APISIX

Get a specific APISIX Consumer by username

get

Get consumer group on Apache APISIX

Get a specific APISIX Consumer Group by ID

get

Get control healthcheck on Apache APISIX

Get health status of all upstream nodes

get

Get control resource healthcheck on Apache APISIX

Get health status for a specific resource

get

Get control schema on Apache APISIX

Get JSON schemas for all resources and enabled plugins

get

Get global rule on Apache APISIX

Get a specific APISIX Global Rule by ID

get

Get plugin config on Apache APISIX

Get a specific APISIX Plugin Config by ID

get

Get proto on Apache APISIX

Get a specific APISIX Proto by ID

get

Get route on Apache APISIX

Get a specific APISIX Route by ID

get

Get service on Apache APISIX

Get a specific APISIX Service by ID

get

Get ssl on Apache APISIX

Get a specific APISIX SSL certificate by ID

get

Get stream route on Apache APISIX

Get a specific APISIX Stream Route by ID

get

Get upstream on Apache APISIX

Get a specific APISIX Upstream by ID

list

List consumer groups on Apache APISIX

List APISIX Consumer Groups

list

List consumers on Apache APISIX

List APISIX Consumers

list

List global rules on Apache APISIX

List APISIX Global Rules

list

List plugin configs on Apache APISIX

List APISIX Plugin Configs

list

List protos on Apache APISIX

List APISIX Protos (Protocol Buffers)

list

List routes on Apache APISIX

List APISIX Routes

list

List services on Apache APISIX

List APISIX Services

list

List ssls on Apache APISIX

List APISIX SSL certificates

list

List stream routes on Apache APISIX

List APISIX Stream Routes (L4 routing)

list

List upstreams on Apache APISIX

List APISIX Upstreams

put

Put consumer on Apache APISIX

Create or update an APISIX Consumer

put

Put consumer group on Apache APISIX

Create or update an APISIX Consumer Group

put

Put global rule on Apache APISIX

Create or update an APISIX Global Rule

put

Put plugin config on Apache APISIX

Create or update an APISIX Plugin Config

put

Put proto on Apache APISIX

Create or update an APISIX Proto

put

Put route on Apache APISIX

Create or update an APISIX Route

put

Put service on Apache APISIX

Create or update an APISIX Service

put

Put ssl on Apache APISIX

Create or update an APISIX SSL certificate

put

Put stream route on Apache APISIX

Create or update an APISIX Stream Route

put

Put upstream on Apache APISIX

Create or update an APISIX Upstream

reload

Reload control plugins on Apache APISIX

Trigger a hot reload of plugins

trigger

Trigger control gc on Apache APISIX

Trigger full garbage collection in the HTTP Lua VM

Connect Apache APISIX to Claude Desktop via MCP

Follow these steps to wire Apache APISIX into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Apache APISIX

Look for the 🔌 icon in the chat. your 50 tools are now available

Why Use Claude Desktop with the Apache APISIX MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Apache APISIX through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Apache APISIX + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Apache APISIX MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Apache APISIX in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Apache APISIX immediately.

"List all active routes in my APISIX gateway."

"Show me the configuration for upstream ID 'backend-cluster'."

"List all consumers to check who has access to the API."

Troubleshooting Apache APISIX MCP Server with Claude Desktop

Common issues when connecting Apache APISIX to Claude Desktop through Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Apache APISIX + Claude Desktop FAQ

Common questions about integrating Apache APISIX MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.