MCP Konnect MCP Server

Kong Konnect MCP Server. That is what the mcp konnect mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server for interacting with Kong Konnect APIs, allowing AI assistants to query and analyze Kong Gateway configurations, traffic, and analytics.

This project provides a Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with Kong Konnect's API Gateway. It offers a set of tools to query analytics data, inspect configuration details, and manage control planes through natural language conversation.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 12 tools. What each one is for:

• timeRange — Time range for data retrieval (15M, 1H, 6H, 12H, 24H, 7D)
• statusCodes — Filter by specific HTTP status codes
• excludeStatusCodes — Exclude specific HTTP status codes
• httpMethods — Filter by HTTP methods
• consumerIds — Filter by consumer IDs
• serviceIds — Filter by service IDs
• routeIds — Filter by route IDs
• maxResults — Maximum number of results to return
• MacOS — ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows — %APPDATA%\Claude\claude_desktop_config.json
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server

What it needs from you

Configuration is passed through the environment: KONNECT_ACCESS_TOKEN, KONNECT_REGION, CONTROL_PLANE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 20 or higher - A Kong Konnect account with API access - A client with MCP capabilities (e.g. Claude Desktop, Cursor, etc...)

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Konnect.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Konnect's toolset — timeRange, statusCodes, excludeStatusCodes and 9 more — is a fair guide to whether it matches your workflow. It is maintained by Kong; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.