4,000+ servers built on vurb.ts
Vinkius

Kong Gateway MCP Server for VS Code CopilotGive VS Code Copilot instant access to 40 tools to Create Certificate, Create Consumer, Create Plugin, 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 Kong Gateway MCP Server for VS Code Copilot is a standout in the Friends Mcp category — giving your AI agent 40 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": {
    "kong-gateway": {
      "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 Kong Gateway 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
Kong Gateway
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 Kong Gateway MCP Server

Connect your Kong Gateway Admin API to any AI agent and take full control of your API management lifecycle through natural conversation.

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

What you can do

  • Services & Routes — List, create, and update upstream services and their associated routing rules to manage traffic flow.
  • Consumer Management — Query and manage API consumers, allowing you to track users and applications interacting with your gateway.
  • Plugin Configuration — Inspect and manage plugins for authentication, rate limiting, and logging across your services and routes.
  • Upstreams & Targets — Configure load balancing by managing upstreams and their health-checked targets.
  • SSL/TLS Management — List and update certificates and SNIs to ensure secure communication across your endpoints.
  • System Health — Retrieve real-time status and information about your Kong instance to monitor performance.

The Kong Gateway MCP Server exposes 40 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 40 Kong Gateway tools available for VS Code Copilot

When VS Code Copilot connects to Kong Gateway through Vinkius, your AI agent gets direct access to every tool listed below — spanning api-gateway, microservices, traffic-management, 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.

create

Create certificate on Kong Gateway

Create a new Kong Certificate

create

Create consumer on Kong Gateway

Create a new Kong Consumer

create

Create plugin on Kong Gateway

Create a new Kong Plugin

create

Create route on Kong Gateway

Create a new Kong Route

create

Create service on Kong Gateway

Create a new Kong Service

create

Create sni on Kong Gateway

Create a new Kong SNI

create

Create target on Kong Gateway

Create a new Target for an Upstream

create

Create upstream on Kong Gateway

Create a new Kong Upstream

delete

Delete certificate on Kong Gateway

Delete a Kong Certificate

delete

Delete consumer on Kong Gateway

Delete a Kong Consumer

delete

Delete plugin on Kong Gateway

Delete a Kong Plugin

delete

Delete route on Kong Gateway

Delete a Kong Route

delete

Delete service on Kong Gateway

Delete a Kong Service

delete

Delete sni on Kong Gateway

Delete a Kong SNI

delete

Delete target on Kong Gateway

Delete a Target from an Upstream

delete

Delete upstream on Kong Gateway

Delete a Kong Upstream

get

Get certificate on Kong Gateway

Get details for a specific Kong Certificate

get

Get consumer on Kong Gateway

Get details for a specific Kong Consumer

get

Get info on Kong Gateway

Retrieve general information about the Kong node

get

Get plugin on Kong Gateway

Get details for a specific Kong Plugin

get

Get route on Kong Gateway

Get details for a specific Kong Route

get

Get service on Kong Gateway

Get details for a specific Kong Service

get

Get sni on Kong Gateway

Get details for a specific Kong SNI

get

Get status on Kong Gateway

Retrieve the status of the Kong node

get

Get upstream on Kong Gateway

Get details for a specific Kong Upstream

list

List certificates on Kong Gateway

List all Kong Certificates

list

List consumers on Kong Gateway

List all Kong Consumers

list

List plugins on Kong Gateway

List all Kong Plugins

list

List routes on Kong Gateway

List all Kong Routes

list

List services on Kong Gateway

List all Kong Services

list

List snis on Kong Gateway

List all Kong SNIs

list

List targets on Kong Gateway

List all Targets for an Upstream

list

List upstreams on Kong Gateway

List all Kong Upstreams

update

Update certificate on Kong Gateway

Update an existing Kong Certificate

update

Update consumer on Kong Gateway

Update an existing Kong Consumer

update

Update plugin on Kong Gateway

Update an existing Kong Plugin

update

Update route on Kong Gateway

Update an existing Kong Route

update

Update service on Kong Gateway

Update an existing Kong Service

update

Update sni on Kong Gateway

Update an existing Kong SNI

update

Update upstream on Kong Gateway

Update an existing Kong Upstream

Connect Kong Gateway to VS Code Copilot via MCP

Follow these steps to wire Kong Gateway 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 Kong Gateway

Ask Copilot: "Using Kong Gateway, help me...". 40 tools available

Why Use VS Code Copilot with the Kong Gateway MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Kong Gateway 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

Kong Gateway + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Kong Gateway 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 Kong Gateway in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Kong Gateway immediately.

01

"List all services currently configured in Kong."

02

"Create a new service named 'auth-api' pointing to 'http://auth.internal'."

03

"What is the current status of my Kong Gateway node?"

Troubleshooting Kong Gateway MCP Server with VS Code Copilot

Common issues when connecting Kong Gateway 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.

Kong Gateway + VS Code Copilot FAQ

Common questions about integrating Kong Gateway 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 →