Overview
What is Kong Konnect MCP Server?
A Model Context Protocol (MCP) server for interacting with Kong Konnect APIs, enabling AI assistants to query and analyze Kong Gateway configurations, traffic, and analytics. The project is deprecated and no longer maintained; users are directed to the Konnect remote MCP server.
How to use Kong Konnect MCP Server?
Install Node.js 20+ and clone the repository. Install dependencies, set the KONNECT_ACCESS_TOKEN environment variable (and optionally KONNECT_REGION), then configure a compatible MCP client (e.g., Claude Desktop) by adding the server to its configuration file. The server exposes tools for analytics, configuration, and control planes.
Key features of Kong Konnect MCP Server
- Query API request analytics with customizable filters
- List and inspect gateway services, routes, consumers, and plugins
- Manage control planes and control plane groups
- Integration with Claude and other MCP‑compatible AI assistants
Use cases of Kong Konnect MCP Server
- Analyzing API traffic by time range, status code, or service
- Troubleshooting consumer issues by inspecting their request patterns
- Listing and inspecting gateway configurations across control planes
- Checking control plane group memberships and details
FAQ from Kong Konnect MCP Server
What are the runtime requirements?
Node.js 20 or higher, a Kong Konnect account with API access, and an MCP‑capable client (e.g., Claude Desktop, Cursor).
How is authentication handled?
Set the KONNECT_ACCESS_TOKEN environment variable with a valid Kong Konnect API key. The optional KONNECT_REGION variable specifies the API region (defaults to US).
Where does the data live?
All data is retrieved live from the Kong Konnect API. No local persistence or caching is provided.
Is this server still maintained?
No. The repository is deprecated and archived as read‑only. Users should migrate to the Konnect remote MCP server.
