Kong Konnect MCP

Kong's Konnect MCP server gives an agent read access to the API gateway control plane, covering both the configuration and the traffic that flows through it. On the configuration side it lists control planes and the services, routes, consumers and plugins defined on each, which makes it possible to answer questions like which routes have no rate limiting attached or which consumers can reach a given service. On the traffic side it reaches Konnect analytics for request volume, latency percentiles and error rates, sliced by service, route, consumer or time window. The practical value is investigation. An agent can start from a symptom such as elevated 5xx errors on one route and walk the chain: find the route, see which upstream service it targets, list the plugins sitting in the request path, then check whether the error rate lines up with a configuration change. It can also summarize a gateway estate that has grown across teams, which is the usual state of a platform with many control planes and no single owner of the whole picture. It targets platform and API teams running Kong Konnect who want that investigation in a chat client or IDE instead of the Konnect UI. The server is read oriented, which is a deliberate safety choice: an agent can explain and diagnose gateway behavior without being able to reconfigure production routing.