4,000+ servers built on vurb.ts
Vinkius

Apache APISIX MCP Server for CursorGive Cursor instant access to 50 tools to Delete Consumer, Delete Consumer Group, Delete Global Rule, and more

MCP Inspector GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

The Apache APISIX MCP Server for Cursor 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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "apache-apisix": {
      "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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Apache APISIX
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.

Cursor's Agent mode turns Apache APISIX into an in-editor superpower. Ask Cursor to generate code using live data from Apache APISIX and it fetches, processes, and writes. all in a single agentic loop. 50 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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 Cursor 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 Cursor

When Cursor 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 Cursor via MCP

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

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
03

Save the file

Cursor will automatically detect the new MCP server
04

Start using Apache APISIX

Open Agent mode in chat and ask: "Using Apache APISIX, help me...". 50 tools available

Why Use Cursor with the Apache APISIX MCP Server

Cursor AI Code Editor provides unique advantages when paired with Apache APISIX through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Apache APISIX + Cursor Use Cases

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

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for Apache APISIX in Cursor

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

01

"List all active routes in my APISIX gateway."

02

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

03

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

Troubleshooting Apache APISIX MCP Server with Cursor

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

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Apache APISIX + Cursor FAQ

Common questions about integrating Apache APISIX MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →