4,000+ servers built on vurb.ts
Vinkius

Kong Gateway MCP Server for Claude DesktopGive Claude Desktop instant access to 40 tools to Create Certificate, Create Consumer, Create Plugin, and more

MCP Inspector GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

The Kong Gateway MCP Server for Claude Desktop 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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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.

Claude Desktop is the definitive way to connect Kong Gateway to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 40 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop

When Claude Desktop 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 Claude Desktop via MCP

Follow these steps to wire Kong Gateway into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using Kong Gateway

Look for the 🔌 icon in the chat. your 40 tools are now available

Why Use Claude Desktop with the Kong Gateway MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Kong Gateway through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Kong Gateway + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Kong Gateway MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Kong Gateway in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

Common issues when connecting Kong Gateway to Claude Desktop through Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Kong Gateway + Claude Desktop FAQ

Common questions about integrating Kong Gateway MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Explore More MCP Servers

View all →