Apache APISIX Connector for AI agents.

50 live capabilities

Manage your cloud-native API gateway routes and traffic rules with natural language.

Live agent request Apache APISIX / Connector

Waiting for input…

AI Agent

Why people use Apache APISIX

Apache APISIX Gateway Management for DevOps Teams

This Connector lets you handle those changes through a simple chat. You describe the route you need, and the agent handles the APISIX Admin API calls for you. You get a faster way to deploy infrastructure without the risk of manual syntax errors.

What Vinkius changes

You get a natural language interface for your entire APISIX gateway infrastructure.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

Real-world use case 01

Rapid Incident Response

An SRE notices a spike in 500 errors.
Real-world use case 02

Fast API Deployment

A developer needs to deploy a new endpoint.
Real-world use case 03

Security Access Audit

A security lead wants to see who has access to the production API.

Complete set · 50capabilities

The complete Apache APISIX capability set.

These are the exact actions your AI can choose when you ask it to work with Apache APISIX.

Capability set01 / 13

01—04

4 capabilities in this set.

Part of 50 available through Apache APISIX.

01 Capability
Delete ssl
Deletes a specific APISIX SSL certificate. Use this to remove expired or unused certificates.
02 Capability
Delete upstream
Deletes a specific APISIX Upstream. Use this to remove a backend cluster from your configuration.
03 Capability
Dump control discovery
Provides a memory dump of discovered service endpoints. This is great for debugging service discovery.
04 Capability
Dump control routes
Dumps all configured Routes from the Control API. This gives you a full list of your API paths.

Capability set02 / 13

05—08

4 capabilities in this set.

Part of 50 available through Apache APISIX.

05 Capability
Dump control services
Dumps all configured Services from the Control API. This shows how your backend services are organized.
06 Capability
Get consumer group
Retrieves a specific APISIX Consumer Group by ID. Use this to check group-level permissions.
07 Capability
Get consumer
Retrieves a specific APISIX Consumer by username. This helps you find a specific user's access level.
08 Capability
Get control schema
Retrieves JSON schemas for all resources and enabled plugins. Use this to understand the required config structure.

Capability set03 / 13

09—12

4 capabilities in this set.

Part of 50 available through Apache APISIX.

09 Capability
Get plugin config
Retrieves a specific APISIX Plugin Config by ID. This shows you the specific settings for a plugin.
10 Capability
Get proto
Retrieves a specific APISIX Proto by ID. Use this to check your custom protocol settings.
11 Capability
Get ssl
Retrieves a specific APISIX SSL certificate by ID. This shows you the details of a specific certificate.
12 Capability
List consumers
Lists all APISIX Consumers. This provides a full list of users with API access.

Capability set04 / 13

13—16

4 capabilities in this set.

Part of 50 available through Apache APISIX.

13 Capability
List global rules
Lists all APISIX Global Rules. Use this to see rules that apply across your entire gateway.
14 Capability
List plugin configs
Lists all APISIX Plugin Configs. This shows all the active logic like auth or rate limiting.
15 Capability
List protos
Lists all APISIX Protos. Use this to see your custom protocol definitions.
16 Capability
List routes
Lists all APISIX Routes. This is the fastest way to see your entire API surface area.

Capability set05 / 13

17—20

4 capabilities in this set.

Part of 50 available through Apache APISIX.

17 Capability
List services
Lists all APISIX Services. Use this to see how your backends are grouped.
18 Capability
List ssls
Lists all APISIX SSL certificates. Use this to manage your certificate inventory.
19 Capability
List stream routes
Lists all APISIX Stream Routes for L4 routing. Use this to see your TCP/UDP routing setup.
20 Capability
Put route
Creates or updates an APISIX Route. This is how you map URLs to your backend services.

Capability set06 / 13

21—24

4 capabilities in this set.

Part of 50 available through Apache APISIX.

21 Capability
Put service
Creates or updates an APISIX Service. This groups your upstream nodes into logical units.
22 Capability
Put ssl
Creates or updates an APISIX SSL certificate. This manages your gateway's encryption keys.
23 Capability
Put upstream
Creates or updates an APISIX Upstream. This is how you manage your backend clusters.
24 Capability
Trigger control gc
Triggers a full garbage collection in the HTTP Lua VM. Use this to clear memory during high load.

Capability set07 / 13

25—28

4 capabilities in this set.

Part of 50 available through Apache APISIX.

25 Capability
Delete stream route
Deletes a specific APISIX Stream Route. This removes L4 routing configurations.
26 Capability
Dump control plugin metadatas
Dumps all plugin metadata from the Control API. Use this to audit what plugins are active.
27 Capability
Get control resource healthcheck
Retrieves the health status for a specific resource. Use this to check a single cluster's health.
28 Capability
List consumer groups
Lists all APISIX Consumer Groups. Use this to see how your users are tiered.

Capability set08 / 13

29—32

4 capabilities in this set.

Part of 50 available through Apache APISIX.

29 Capability
List upstreams
Lists all configured APISIX Upstreams. This shows you all the backend pools currently managed.
30 Capability
Put proto
Creates or updates an APISIX Proto. Use this to manage custom protocol configurations.
31 Capability
Reload control plugins
Triggers a hot reload of all plugins. Use this to apply changes without restarting the gateway.
32 Capability
Dump control upstreams
Lists all configured upstreams from the Control API. This helps you see your entire backend pool at once.

Capability set09 / 13

33—36

4 capabilities in this set.

Part of 50 available through Apache APISIX.

33 Capability
Get global rule
Retrieves a specific APISIX Global Rule by ID. Use this to check high-level traffic settings.
34 Capability
Get route
Fetches the details of a specific APISIX Route by ID. This is useful for inspecting specific path configurations.
35 Capability
Get service
Retrieves a specific APISIX Service by its ID. Use this to see how your services are grouped.
36 Capability
Get stream route
Fetches a specific APISIX Stream Route by ID. This is for inspecting L4 routing configurations.

Capability set10 / 13

37—40

4 capabilities in this set.

Part of 50 available through Apache APISIX.

37 Capability
Get upstream
Retrieves a specific APISIX Upstream by ID. This shows you the individual nodes in a cluster.
38 Capability
Delete consumer group
Removes an existing APISIX Consumer Group. Use this to clean up old access tiers.
39 Capability
Delete consumer
Deletes a specific APISIX Consumer from the system. This removes individual access keys.
40 Capability
Delete global rule
Removes a specific APISIX Global Rule. Use this to clear gateway-wide settings.

Capability set11 / 13

41—44

4 capabilities in this set.

Part of 50 available through Apache APISIX.

41 Capability
Delete plugin config
Deletes an APISIX Plugin Configuration. This removes specific logic like rate limiting or auth.
42 Capability
Delete proto
Removes an APISIX Proto from the configuration. This cleans up your custom protocol definitions.
43 Capability
Delete route
Deletes a specific APISIX Route. Use this to remove old API paths from your gateway.
44 Capability
Put consumer group
Creates or updates an APISIX Consumer Group. This manages how different user tiers are handled.

Capability set12 / 13

45—47

3 capabilities in this set.

Part of 50 available through Apache APISIX.

45 Capability
Put consumer
Creates or updates an APISIX Consumer. Use this to manage API keys and user permissions.
46 Capability
Put global rule
Creates or updates an APISIX Global Rule. This applies settings to all traffic across the gateway.
47 Capability
Put plugin config
Creates or updates an APISIX Plugin Configuration. This lets you tweak specific features like auth or logging.

Capability set13 / 13

48—50

3 capabilities in this set.

Part of 50 available through Apache APISIX.

48 Capability
Delete service
Deletes a specific APISIX Service. Use this to remove a backend service group from the gateway.
49 Capability
Get control healthcheck
Retrieves the health status of all upstream nodes. This is your go-to for checking backend availability.
50 Capability
Put stream route
Creates or updates an APISIX Stream Route. Use this for managing L4 traffic.

Set up in minutes

One URL. Then ask Apache APISIX to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Apache APISIX from the conversation.

Choose your client

Live preview

Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp

Step 01

Open Connectors

In Claude Web or Claude Desktop, open Settings and choose Connectors.
Step 02

Add the URL

Choose Add custom connector, name it Apache APISIX, and paste the URL above.
Step 03

Turn it on in chat

Select +, open Connectors, and enable Apache APISIX for the conversation.

ChatGPT · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP

https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp

Step 01

Open MCP settings

On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
Step 02

Add the URL

Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Apache APISIX URL.
Step 03

Save and start

Save the connection and enable Apache APISIX in your conversation. Desktop may ask you to restart once.

Cursor · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "apache-apisix": {
      "url": "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"
    }
  }
}

Step 01

Open MCP Settings

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

Add the server config

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

Save the file

Cursor will automatically detect the new Connector
Step 04

Start using Apache APISIX

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

VS Code Copilot · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "apache-apisix": {
      "url": "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"
    }
  }
}

Step 01

Create MCP config

Create a .vscode/mcp.json file in your project root
Step 02

Add the server config

Paste the JSON configuration above
Step 03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
Step 04

Start using Apache APISIX

Ask Copilot: "Using Apache APISIX, help me...". 50 tools available

Windsurf · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "apache-apisix": {
      "url": "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"
    }
  }
}

Step 01

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
Step 02

Add the server

Paste the JSON configuration above into mcp_config.json
Step 03

Save and reload

Windsurf will detect the new server automatically
Step 04

Start using Apache APISIX

Open Cascade and ask: "Using Apache APISIX, help me...". 50 tools available

Cline · IDE configuration

Official guide ↗

Advanced setup

{
  "mcpServers": {
    "apache-apisix": {
      "url": "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"
    }
  }
}

Step 01

Open Cline MCP Settings

Click the Connectors icon in the Cline sidebar panel
Step 02

Add remote server

Click "Add Connector" and paste the configuration above
Step 03

Enable the server

Toggle the server switch to ON
Step 04

Start using Apache APISIX

Ask Cline: "Using Apache APISIX, help me...". 50 tools available

Claude Code · Terminal command

Official guide ↗

Advanced setup

claude mcp add apache-apisix --transport http "https://edge.vinkius.com/vk_preview_uvuQ6vDEh3EK8RpcSSCqKlnF1NufI3SlkBIczBCN/mcp"

Step 01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed
Step 02

Add the Connector

Run the command above in your terminal
Step 03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session
Step 04

Start using Apache APISIX

Ask Claude: "Using Apache APISIX, show me...". 50 tools are ready

Where the request belongs

Work Apache APISIX can move forward.

Built around the request

This is for the DevOps engineer who's tired of clicking through dashboards at 2am to fix a routing loop, or the backend developer who wants to deploy new API endpoints without waiting for a manual config update.

01

DevOps Engineer

Audits routing rules and checks upstream health during incidents.

02

Backend Developer

Creates and tests new API routes directly from the IDE.

03

SRE Team Member

Troubleshoots traffic flow issues and consumer access problems using chat.

Build the capability set

Each Connector adds new actions and data without changing how you work.

Browse Connectors

01 40 capabilities

Kong Gateway

Manage your API Gateway infrastructure. list services, configure routes, and manage consumers or plugins directly from any AI agent.

02 10 capabilities

Kong (AI API Gateway)

Manage your API Gateway via Kong. orchestrate services, routes, and AI plugins directly from your agent.

03 8 capabilities

Traefik Hub

Cloud-native API Management & Gateway evaluating proxy topologies explicitly running Kubernetes integrations.

04 18 capabilities

Traefik Proxy

Monitor and manage your Traefik Proxy infrastructure. inspect routers, services, and middlewares directly from your AI agent.

05 12 capabilities

Tyk

Manage your Tyk API Gateway and Dashboard. create keys, manage security policies, and list API definitions via natural language.

06 10 capabilities

Zuplo

Manage API gateways, edge deployments, and consumers on Zuplo. the programmable API management platform for developers.

Bring your own AI

Change the model, client or framework. Keep Apache APISIX connected.

Before you connect

Questions about Apache APISIX.

The practical details behind the request, access and result.

What is the Apache APISIX MCP for?

It lets you manage your API gateway using natural language. Instead of writing JSON or using a dashboard, you can tell your AI agent to create routes, manage upstreams, and handle traffic rules.

Can I use this to manage my SSL certificates?

Yes, you can use the Connector to create or update SSL certificates through your AI client. It makes it much easier to keep your gateway secure without manually handling certificate files.

How do I connect my gateway to this Connector?

You just need your APISIX Admin URL and your Admin Key. Once you provide those to your AI client, you can start managing your routes and services immediately.

Does this Connector support load balancing?

Yes, it lets you manage upstreams, which handle your load balancing logic. You can ask your agent to configure node weights, health checks, and balancing algorithms.

Can I use this to troubleshoot my gateway?

Absolutely. You can ask the agent to list routes, check the health of your upstream nodes, or dump the current configuration to see exactly how traffic is flowing.

Is this suitable for production environments?

Yes, it interacts with the official APISIX Admin API. It's a way to perform standard management tasks like route creation and consumer updates through a conversational interface.

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.

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.

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.

One connection away

Give your agent a direct line to Apache APISIX.

Connect Apache APISIX once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available