4,000+ servers built on vurb.ts
Vinkius

Apache APISIX MCP Server for VS Code CopilotGive VS Code Copilot instant access to 50 tools to Delete Consumer, Delete Consumer Group, Delete Global Rule, and more

MCP Inspector GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

The Apache APISIX MCP Server for VS Code Copilot 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.

GitHub Copilot Agent mode brings Apache APISIX data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 50 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot

When VS Code Copilot 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 VS Code Copilot via MCP

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

01

Create MCP config

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

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

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

Start using Apache APISIX

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

Why Use VS Code Copilot with the Apache APISIX MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Apache APISIX through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Apache APISIX + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Apache APISIX MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Apache APISIX in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Apache APISIX to VS Code Copilot through Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Apache APISIX + VS Code Copilot FAQ

Common questions about integrating Apache APISIX MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Explore More MCP Servers

View all →