mcp-konnect

Kong Konnect MCP Server exposes a set of tools to interact with Kong Konnect's API Gateway via natural language. The server enables AI assistants to query API traffic analytics, inspect gateway configurations (services, routes, consumers, plugins), and manage control planes and groups associated with your Konnect organization. Tools are organized into Analytics, Configuration, and Control Planes categories, allowing you to retrieve filtered analytics data, enumerate configuration objects, and manage control-plane memberships through conversational prompts. When connected to a Claude-like MCP client, you can invoke specific tools by describing the data you want (for example: list services for a given control plane, or show API requests for a service in the last hour). The included example configuration demonstrates how Claude or similar tools can initialize the MCP server with the proper environment variables for authentication and regional targeting.

Prerequisites:

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

Installation steps:

1. Clone the repository

git clone https://github.com/Kong/mcp-konnect.git
cd mcp-konnect

2. Install dependencies

npm install

3. Build the project

npm run build

4. Run the MCP server (example)

# Ensure environment variables are set with your Konnect credentials
export KONNECT_ACCESS_TOKEN=kpat_api_key_here
export KONNECT_REGION=us

# Start the server (adjust paths as needed)
node build/index.js

5. Integrate with your MCP client (e.g., Claude Desktop) using the provided configuration snippet demonstrating how to point to the built index.js and pass credentials.

Environment variables:

• KONNECT_ACCESS_TOKEN: Required for Kong Konnect API access
• KONNECT_REGION: Optional; defaults to US if not set (values: US, EU, AU, ME, IN)

Configuration tips:

• Use absolute paths for the server entry (build/index.js) when configuring MCP clients.
• Keep access tokens secure; do not commit them to source control.
• If you update code and rebuild, ensure the MCP client points to the new build/index.js path.

Common issues:

• Authentication errors: verify the API key is valid and has the necessary permissions; ensure KONNECT_REGION matches your account region.
• Network failures: confirm network access to Kong Konnect endpoints and proper token scoping.
• Data not found: verify IDs and time ranges used in analytics queries refer to resources in your Konnect organization.

Development tips:

• Follow the repository's development steps to add new tools or modify existing ones in tools.ts, parameters.ts, and operations/ directory as described in the README.