An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Apache APISIX to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Control complex microservices infrastructure via conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 50 capabilities

We ship only the actions that matter.

Capability set01 / 13

01-04

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 01

    Delete upstream

    Removes a specific Upstream configuration from your gateway.

  2. 02

    Dump control routes

    Retrieves a full list of all configured Routes from the Control API.

  3. 03

    Dump control services

    Retrieves a full list of all configured Services from the Control API.

  4. 04

    Get consumer group

    Fetches the details for a specific Consumer Group using its ID.

Capability set02 / 13

05-08

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 05

    Get control schema

    Gets the JSON schemas for all resources and enabled plugins, helping you understand the API structure.

  2. 06

    Get proto

    Retrieves the details for a specific APISIX Proto by ID.

  3. 07

    List consumers

    Lists all active APISIX Consumers, showing who has access to the API.

  4. 08

    List plugin configs

    Lists all configured plugins, letting you audit your gateway's extensions.

Capability set03 / 13

09-12

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 09

    List protos

    Lists all available APISIX Protos (Protocol Buffers) in the system.

  2. 10

    List services

    Lists all defined APISIX Services, which group common configurations.

  3. 11

    List stream routes

    Lists Layer 4 (L4) routing rules defined in the Stream Routes.

  4. 12

    Put route

    Creates or updates an APISIX Route, defining how client requests are matched and forwarded.

Capability set04 / 13

13-16

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 13

    Put ssl

    Creates or updates an SSL certificate for your gateway.

  2. 14

    Put upstream

    Creates or updates an Upstream configuration, defining where traffic should go.

  3. 15

    Trigger control gc

    Runs a garbage collection cycle on the HTTP Lua VM to clear memory and improve stability.

  4. 16

    Dump control plugin metadatas

    Retrieves metadata for all plugins configured in the Control API.

Capability set05 / 13

17-20

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 17

    List consumer groups

    Lists all defined APISIX Consumer Groups.

  2. 18

    List upstreams

    Lists all configured Upstreams, showing the backend nodes available for load balancing.

  3. 19

    Put proto

    Creates or updates an APISIX Proto definition.

  4. 20

    Reload control plugins

    Triggers a hot reload of plugins, applying changes without restarting the gateway.

Capability set06 / 13

21-24

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 21

    Dump control upstreams

    Retrieves a full dump of all configured Upstreams from the Control API.

  2. 22

    Get service

    Fetches the details for a specific APISIX Service by its ID.

  3. 23

    Delete global rule

    Deletes a specific Global Rule that affects all traffic.

  4. 24

    Delete consumer group

    Deletes an entire APISIX Consumer Group.

Capability set07 / 13

25-28

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 25

    Delete plugin config

    Deletes a specific Plugin Configuration.

  2. 26

    Delete route

    Deletes a specific APISIX Route.

  3. 27

    Put global rule

    Creates or updates a Global Rule that applies across the entire gateway.

  4. 28

    Put consumer group

    Creates or updates an APISIX Consumer Group.

Capability set08 / 13

29-32

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 29

    Put plugin config

    Creates or updates a Plugin Configuration.

  2. 30

    Delete service

    Deletes a specific APISIX Service.

  3. 31

    Get control healthcheck

    Checks the health status of all upstream nodes in the gateway.

  4. 32

    Delete consumer

    Deletes a specific APISIX Consumer.

Capability set09 / 13

33-36

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 33

    Delete proto

    Deletes an APISIX Proto definition.

  2. 34

    Delete ssl

    Deletes an APISIX SSL certificate.

  3. 35

    Delete stream route

    Deletes a specific APISIX Stream Route.

  4. 36

    Dump control discovery

    Performs a memory dump of discovered service endpoints for debugging.

Capability set10 / 13

37-40

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 37

    Get consumer

    Fetches the details for a specific APISIX Consumer using a username.

  2. 38

    Get control resource healthcheck

    Checks the health status for a specific resource within the gateway.

  3. 39

    Get global rule

    Fetches the details for a specific Global Rule by its ID.

  4. 40

    Get plugin config

    Fetches the details for a specific Plugin Configuration by ID.

Capability set11 / 13

41-44

4 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 41

    Get route

    Fetches the details for a specific APISIX Route by its ID.

  2. 42

    Get ssl

    Fetches the details for a specific APISIX SSL certificate by ID.

  3. 43

    Get stream route

    Fetches the details for a specific APISIX Stream Route by its ID.

  4. 44

    Get upstream

    Fetches the details for a specific APISIX Upstream by its ID.

Capability set12 / 13

45-47

3 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 45

    List global rules

    Lists all configured Global Rules across the gateway.

  2. 46

    List routes

    Lists all configured APISIX Routes.

  3. 47

    List ssls

    Lists all managed APISIX SSL certificates.

Capability set13 / 13

48-50

3 capabilities in this set.

Part of 50 available through Apache APISIX.

  1. 48

    Put consumer

    Creates or updates an APISIX Consumer, managing user access and rate limits.

  2. 49

    Put service

    Creates or updates an APISIX Service, grouping related upstream configurations.

  3. 50

    Put stream route

    Creates or updates an APISIX Stream Route for Layer 4 traffic management.

Real work

What teams actually run

01

Debugging a Failed Request

A request fails. You ask the agent to check the health status of the relevant upstream nodes, immediately pinpointing if the issue is network-related.

02

Updating Rate Limits

A client needs higher access. You instruct the agent to update the consumer's rate limit and associated authentication plugin.

03

Adding a New API Endpoint

You need a new service. You ask the agent to create a new service abstraction and link it to a specific set of upstreams.

04

Auditing Global Rules

Before a deployment, you ask the agent to list all global rules to ensure no unexpected traffic behavior is possible.

Automate a task

Put Apache APISIX to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Apache APISIX works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Apache APISIX to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1340ms average. Fast in production.

Apache APISIX is checked daily against the live service.

Daily averagePeak 1681ms
Oct 3Today
Fastest day
1165ms
Slowest day
1681ms
14-day trend
Improving-13%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 50 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Apache APISIX, so you can see the experience inside your AI.

It does not authenticate your account with Apache APISIX. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Apache APISIX Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Apache APISIX capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "apache-apisix-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Apache APISIX in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Apache APISIX owners hand off.

This MCP is built for engineers who manage complex, high-traffic microservices. If you spend time debugging routing rules, checking load balancer health, or updating API access controls, this capability is for you. It lets you treat your entire API Gateway like a conversation.

  • 01

    DevOps Engineer

    Quickly audit routing rules and upstream health directly from your chat interface, eliminating the need to switch to the CLI.

  • 02

    Backend Developer

    Create and test new API routes or service abstractions without leaving your IDE or context.

  • 03

    SRE Team Member

    Troubleshoot traffic flow, check consumer access issues, and trigger necessary hot reloads using natural language queries.

FAQ

Questions Apache APISIX owners ask.

  • 01

    Do I need to use the command line to manage my routes?

    No. This MCP lets you manage routes, services, and upstreams entirely through natural language conversation with your AI agent. You don't have to switch context to the CLI or a dashboard.

  • 02

    What kind of traffic management can I perform?

    You can handle everything from Layer 7 routing rules to Layer 4 stream routes. You can also manage load balancing by configuring upstreams and checking node health.

  • 03

    Is this MCP safe for production use?

    Yes. It provides capabilities to check the health status of all upstream nodes and resources, allowing you to audit the system before making any changes.

  • 04

    Can I see who has access to the API?

    You can list all consumers and consumer groups. This lets you audit which users or applications have access and what rate limits are applied.

  • 05

    What if I need to update a complex configuration?

    You can update complex JSON configurations for any gateway resource. The agent handles the structure, so you just tell it what you want to change.

  • 06

    Can I update a route's configuration directly through the AI?

    Yes. Use the put_route capability by providing the Route ID and the new configuration JSON. The agent will interface with the APISIX Admin API to apply the changes immediately.

  • 07

    How do I list all the backend upstreams configured in my gateway?

    Simply ask the agent to 'list upstreams'. It will trigger the list_upstreams capability and return a detailed list of all virtual hosts and load balancer nodes.

  • 08

    Is it possible to delete a service that is no longer needed?

    Yes, you can use the delete_service capability. Provide the specific Service ID, and the agent will remove the resource from your APISIX configuration.

Explore

More in Loved By Devs

Suggestions

Connect Apache APISIX to Claude, Cursor, ChatGPT & more