4,000+ servers built on vurb.ts
Vinkius
CursorIDE
Kong Gateway MCP Server

Bring Api Gateway
to Cursor

Learn how to connect Kong Gateway to Cursor and start using 40 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create CertificateCreate ConsumerCreate PluginCreate RouteCreate ServiceCreate SniCreate TargetCreate UpstreamDelete CertificateDelete ConsumerDelete PluginDelete RouteDelete ServiceDelete SniDelete TargetDelete UpstreamGet CertificateGet ConsumerGet InfoGet PluginGet RouteGet ServiceGet SniGet StatusGet UpstreamList CertificatesList ConsumersList PluginsList RoutesList ServicesList SnisList TargetsList UpstreamsUpdate CertificateUpdate ConsumerUpdate PluginUpdate RouteUpdate ServiceUpdate SniUpdate Upstream

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Kong Gateway

What is the 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.

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.

How it works

  1. Subscribe to this server
  2. Enter your Kong Admin URL (and optional Admin Token)
  3. Start managing your API infrastructure from Claude, Cursor, or any MCP-compatible client

No more manual cURL commands or navigating complex dashboards to check a route configuration. Your AI acts as a dedicated DevOps engineer or API Architect.

Who is this for?

  • DevOps Engineers — quickly check gateway status, list plugins, and verify upstream health without leaving the terminal or IDE.
  • Backend Developers — create and test new services and routes instantly during the development cycle.
  • API Architects — audit consumer access and plugin configurations to ensure security and compliance across the organization.

Built-in capabilities (40)

create_certificate

Create a new Kong Certificate

create_consumer

Create a new Kong Consumer

create_plugin

Create a new Kong Plugin

create_route

Create a new Kong Route

create_service

Create a new Kong Service

create_sni

Create a new Kong SNI

create_target

Create a new Target for an Upstream

create_upstream

Create a new Kong Upstream

delete_certificate

Delete a Kong Certificate

delete_consumer

Delete a Kong Consumer

delete_plugin

Delete a Kong Plugin

delete_route

Delete a Kong Route

delete_service

Delete a Kong Service

delete_sni

Delete a Kong SNI

delete_target

Delete a Target from an Upstream

delete_upstream

Delete a Kong Upstream

get_certificate

Get details for a specific Kong Certificate

get_consumer

Get details for a specific Kong Consumer

get_info

Retrieve general information about the Kong node

get_plugin

Get details for a specific Kong Plugin

get_route

Get details for a specific Kong Route

get_service

Get details for a specific Kong Service

get_sni

Get details for a specific Kong SNI

get_status

Retrieve the status of the Kong node

get_upstream

Get details for a specific Kong Upstream

list_certificates

List all Kong Certificates

list_consumers

List all Kong Consumers

list_plugins

List all Kong Plugins

list_routes

List all Kong Routes

list_services

List all Kong Services

list_snis

List all Kong SNIs

list_targets

List all Targets for an Upstream

list_upstreams

List all Kong Upstreams

update_certificate

Update an existing Kong Certificate

update_consumer

Update an existing Kong Consumer

update_plugin

Update an existing Kong Plugin

update_route

Update an existing Kong Route

update_service

Update an existing Kong Service

update_sni

Update an existing Kong SNI

update_upstream

Update an existing Kong Upstream

Why Cursor?

Cursor's Agent mode turns Kong Gateway into an in-editor superpower. Ask Cursor to generate code using live data from Kong Gateway and it fetches, processes, and writes. all in a single agentic loop. 40 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

  • Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

  • Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

  • MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

  • VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

Kong Gateway in Cursor

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Kong Gateway and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Kong Gateway to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Kong Gateway in Cursor

The Kong Gateway 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. All 40 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

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

The Vinkius Advantage

How Vinkius secures Kong Gateway for Cursor

Every tool call from Cursor to the Kong Gateway MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How can I check if my Kong Gateway instance is running correctly?

You can use the get_status tool. It will return the current status of the Kong node, including database connectivity and server metrics.

02

Can I list all the plugins currently enabled on my gateway?

Yes! Use the list_plugins tool to retrieve a complete list of all configured plugins across your entire Kong instance.

03

Is it possible to create a new service and its route through the AI?

Absolutely. You can use create_service to define your upstream and then create_route to specify how traffic should reach that service.

04

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

05

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

06

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

07

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

08

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

09

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →