Kong Gateway MCP for AI. Manage your API infrastructure conversationally.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Kong Gateway MCP connects your AI agent directly to your API management layer. Manage all aspects of your traffic flow—from creating new services and defining routes to updating certificates and monitoring system health—using natural conversation instead of cURL commands or dashboard clicks.
What your AI can do
Create certificate
Generates a new SSL/TLS certificate for use within Kong.
Create consumer
Registers and creates a new API consumer identity in the gateway.
Create plugin
Adds a specific functional plugin, like rate limiting or logging, to the system.
Define and configure new backend services that your APIs will connect to.
Set up specific rules, like path matching or header checking, that guide incoming traffic to the correct service.
Create and track API consumers, defining which applications are allowed to hit your gateway.
List, update, or create SSL certificates and SNIs to ensure all traffic is encrypted.
Retrieve real-time status information on the entire Kong instance, including connection counts and uptime.
Ask an AI about this
Waiting for input…
Kong Gateway: 40 Management Tools
Use these tools to perform every CRUD operation needed for managing Kong's complex API infrastructure components.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Kong Gateway on VinkiusCreate Certificate
Generates a new SSL/TLS certificate for use within Kong.
Create Consumer
Registers and creates a new API consumer identity in the gateway.
Create Plugin
Adds a specific functional plugin, like rate limiting or logging, to the system.
Create Route
Establishes a new rule that directs incoming API traffic to a specific service.
Create Service
Defines a new upstream backend service that the gateway will proxy requests to.
Create Sni
Sets up a new Subject Name Ind used for virtual hosting on certificates.
Create Target
Adds a specific backend server address that an upstream can connect to.
Create Upstream
Sets up a new group of backend servers (upstreams) for load balancing.
Delete Certificate
Removes an existing SSL/TLS certificate from the gateway configuration.
Delete Consumer
Permanently removes a registered API consumer identity.
Delete Plugin
Deactivates and removes a plugin from the gateway's configuration.
Delete Route
Removes an existing traffic routing rule from the system.
Delete Service
Deletes a defined backend service, stopping all associated routes.
Delete Sni
Removes an existing Subject Name Ind from the gateway configuration.
Delete Target
Removes a specific backend server address from an upstream group.
Delete Upstream
Deletes the entire upstreams definition, taking down associated targets.
Get Certificate
Retrieves all details for a specific SSL/TLS certificate.
Get Consumer
Fetches the full profile and policy details for an API consumer.
Get Info
Retrieves high-level operational information about the Kong node instance.
Get Plugin
Gets detailed configuration and status for a specific plugin.
Get Route
Fetches all current routing rules, including their conditions and targets.
Get Service
Retrieves the configuration details for a specific backend service.
Get Sni
Gets the Subject Name Ind details, including which certificates it applies to.
Get Status
Checks the overall operational status of the Kong gateway node.
Get Upstream
Retrieves information about a defined upstream group, including its targets.
List Certificates
Lists every certificate currently configured on the gateway.
List Consumers
Provides a list of all active API consumers and their current policies.
List Plugins
Lists every plugin currently installed and configured on the gateway.
List Routes
Shows all active routing rules that are directing traffic through the gateway.
List Services
Lists every defined backend service endpoint available for proxying.
List Snis
Shows all configured Subject Name Inds used for virtual hosting.
List Targets
Lists all backend server targets associated with a specific upstream group.
List Upstreams
Displays every defined upstreams cluster used for load balancing.
Update Certificate
Modifies parameters on an existing SSL/TLS certificate, like renewal dates or keys.
Update Consumer
Changes the policy or scope for an already created API consumer.
Update Plugin
Adjusts settings on a plugin, such as modifying rate limit thresholds.
Update Route
Modifies the rules or destination of an existing traffic route.
Update Service
Updates the connection details for a service, like changing its target host.
Update Sni
Changes metadata on an existing Subject Name Ind record.
Update Upstream
Modifies the settings for a backend upstreams cluster, like adding new targets.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Kong Gateway integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Kong Gateway, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Kong Gateway. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 40 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing gateway settings means endless dashboard navigation.
Today, setting up a simple change requires navigating to the service tab, finding the specific route ID, verifying the current upstream definition, and then clicking through multiple sub-menus just to update a single hostname or consumer policy. It’s constant context switching and copy-pasting IDs.
With this MCP, you describe the change in plain English. You simply tell your agent what needs updating—like modifying an existing route or creating a new service—and it executes the complex sequence of calls behind the scenes. The result is immediate confirmation, no manual dashboard clicks required.
Kong Gateway MCP gives you full control over API infrastructure.
Manual operations mean that updating a certificate requires calling delete_certificate and then create_certificate. Changing an upstream target means deleting the old one with delete_target before creating the new record with create_target.
Now, you treat it like conversation. You ask for the change, and your agent executes the necessary sequence of API calls—whether it's a simple get_status check or a complex update_plugin operation. It’s pure command-line power, guided by chat.
What your AI can actually do with this
You can use this MCP to take full control of your entire API infrastructure lifecycle right from any chat interface. Instead of logging into a complex dashboard just to check if an endpoint is working, you tell your agent what you need done. It handles the details: defining new upstream services, setting up consumer access policies, or checking rate limiting plugins.
Your AI acts like a dedicated DevOps engineer, letting you list all active routes and then create updates on the fly. When you connect this MCP via Vinkius, you gain visibility into everything, from managing SSL/TLS certificates to ensuring load balancing targets are healthy. It simplifies massive infrastructure tasks down to simple conversation.
019e38b5-54cc-7081-8d68-7c33f7337f60 
Here's how it actually works
The bottom line is that your agent handles all the API calls and complex data structures behind the scenes, letting you talk shop instead of writing scripts.
Provide your agent with your Kong Admin URL and any necessary admin tokens.
Tell your agent the infrastructure change you need—for example, 'Create a new service for user profiles pointing to auth.internal.'
The MCP executes the request, confirming if the Service, Route, or Consumer was created, updated, or deleted.
Who is this actually for?
This MCP is for platform engineers, backend developers, and security architects. If you're tired of switching between a terminal, an IDE, and a web dashboard just to make one routing adjustment, this is for you.
Checking the current status, listing plugins, or deleting old resources like services and routes without leaving their primary console.
Testing a new service endpoint by creating a temporary route and verifying its connectivity during development cycles.
Auditing consumer access rights or updating certificate configurations to ensure the entire system meets current security compliance standards.
What Changes When You Connect
You instantly audit security rules. Instead of running curl commands against a dashboard to check consumer access, you ask for details using get_consumer or list_consumers.
Maintenance is faster and safer. Need to change where traffic goes? Use the agent to update_route or create_service instead of manually editing configuration files and risking downtime.
Keep your system secure without leaving your terminal. Check gateway status with get_status or list_certificates, getting real-time data instantly as if you were running a simple command.
Scaling load balancing is straightforward. You can list_upstreams and then use update_upstream to add targets or modify health checks across entire clusters.
Debugging traffic flow gets easy. If something breaks, you can get_route to see the exact rules in place and pinpoint which service definition needs fixing.
See it in action
The Certificate Renewal Headache
The security team knows the certificates are expiring next week. Instead of logging into a separate certificate management portal, they ask their agent to list_certificates and then use update_certificate on the expired key, getting confirmation it's ready for deployment.
Adding a New Microservice
A developer needs a new endpoint. They tell the agent to create_service first, pointing it to the internal IP. Then they use create_route to funnel traffic from /v2/new to that service definition.
Revoking Client Access
A client account is compromised. Instead of manually finding and deleting their credentials, an architect uses the agent to get_consumer details, confirms the scope, and then executes delete_consumer immediately.
The honest tradeoffs
The Dashboard Click Spiral
Trying to update a service's hostname requires clicking into three different tabs on the dashboard, copying an ID from one screen, and pasting it into another. This is slow and prone to copy/paste errors.
Just ask your agent. Tell it: 'Update the upstream for user-service.' It handles the context switching and API calls using update_upstream or update_service.
The cURL Dump
Running a massive, multi-line cURL command to list all routes. This is tedious, hard to read in the terminal history, and difficult to validate if every parameter was correct.
Simply ask your agent: 'List all current routes.' It returns clean, structured data without forcing you to build complex requests.
When It Fits, When It Doesn't
Use this MCP if your job involves managing the lifecycle of networking resources like certificates, routes, or services. You need fine-grained control over resource creation (create_route) and modification (update_consumer). Don't use it if you only want to read general system metrics; for that, a dedicated monitoring tool is better. If you just need basic CRUD access without the API Gateway context, a generic database connector will suffice. But if your concern is traffic flow control, authentication policies, or load balancing definitions, this MCP is exactly what you need.
Questions you might have
How do I list all services with Kong Gateway MCP? +
You use the list_services tool. This gives you a comprehensive rundown of every backend service defined on your gateway that can accept traffic.
Can I delete a route using the get_route or list_routes tools? +
No, those tools only read data. To remove a rule, you must use the delete_route tool to properly decommission the specific traffic path.
What's the difference between create_upstream and update_upstream? +
create_upstream sets up an entirely new cluster of backend servers. update_upstream modifies an existing cluster, perhaps by adding or removing targets without affecting its core definition.
How do I check if a consumer exists using get_consumer? +
You provide the Consumer ID to get_consumer. It returns the full profile and status, confirming whether the account is active and what policies apply.
How do I check which SSL/TLS certificates are available using list_certificates? +
It lists every configured certificate. This lets you confirm that your API endpoints have the necessary secure keys for communication.
If I want to implement rate limiting, how does create_plugin help me manage policies? +
You use this tool to deploy specific plugins like Rate Limiting or Authentication. Once a plugin is active, you control its policy settings for the entire gateway.
What process should I follow if I need to add new backend endpoints using list_targets? +
You first define an upstream group, and then use this command. It connects the logical service definition to a specific set of live server addresses.
How do I check the general operational health of my Kong Gateway node using get_status? +
This command returns real-time performance data for your entire gateway instance. You can quickly verify active connections and overall stability without checking logs.
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.
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.
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.
We've already built the connector for Kong Gateway. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 40 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.