Compatible with every major AI agent and IDE
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
- Subscribe to this server
- Enter your Kong Admin URL (and optional Admin Token)
- 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 a new Kong Certificate
Create a new Kong Consumer
Create a new Kong Plugin
Create a new Kong Route
Create a new Kong Service
Create a new Kong SNI
Create a new Target for an Upstream
Create a new Kong Upstream
Delete a Kong Certificate
Delete a Kong Consumer
Delete a Kong Plugin
Delete a Kong Route
Delete a Kong Service
Delete a Kong SNI
Delete a Target from an Upstream
Delete a Kong Upstream
Get details for a specific Kong Certificate
Get details for a specific Kong Consumer
Retrieve general information about the Kong node
Get details for a specific Kong Plugin
Get details for a specific Kong Route
Get details for a specific Kong Service
Get details for a specific Kong SNI
Retrieve the status of the Kong node
Get details for a specific Kong Upstream
List all Kong Certificates
List all Kong Consumers
List all Kong Plugins
List all Kong Routes
List all Kong Services
List all Kong SNIs
List all Targets for an Upstream
List all Kong Upstreams
Update an existing Kong Certificate
Update an existing Kong Consumer
Update an existing Kong Plugin
Update an existing Kong Route
Update an existing Kong Service
Update an existing Kong SNI
Update an existing Kong Upstream
Why AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Kong Gateway tools. Connect 40 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Kong Gateway tools to solve complex tasks
- —
Role-based architecture lets you assign Kong Gateway tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive Kong Gateway tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes Kong Gateway tool responses in an isolated environment
Kong Gateway in AutoGen
Kong Gateway and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Kong Gateway to AutoGen 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Kong Gateway in AutoGen
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 AutoGen 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.

* 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
How Vinkius secures
Kong Gateway for AutoGen
Every tool call from AutoGen to the Kong Gateway MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Kong Gateway tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"
Explore More MCP Servers
View all →
Dexatel
10 toolsEquip your AI agent to send SMS messages, track communications, and manage contacts via the Dexatel API.

Zilliz Cloud
10 toolsManage vector collections and perform similarity searches via Zilliz Cloud.

World Bank Economy
4 toolsInstantly query GDP, inflation, economic growth, and financial sector indicators from the World Bank. Zero auth required.

BambooHR
12 toolsOfficial HR software automation — manage employee directories, time off requests, and company reports via AI.
