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.
2.2K
10 Tools
Version 4.43 or later needs to be installed to add the server automatically
Tools
Name | Description |
---|---|
query_api_requests | Query and analyze Kong API Gateway requests with customizable filters. Before calling this it's necessary to have a controlPlaneID and a serviceID or routeID. These can be obtained using the list-control-planes, list-services, and list-routes tools. INPUT: - timeRange: String - Time range for data retrieval (15M, 1H, 6H, 12H, 24H, 7D) - statusCodes: Number[] (optional) - Filter by specific HTTP status codes - excludeStatusCodes: Number[] (optional) - Exclude specific HTTP status codes - httpMethods: String[] (optional) - Filter by HTTP methods (e.g., GET, POST) - consumerIds: String[] (optional) - Filter by consumer IDs - serviceIds: String[] (optional) - Filter by service IDs. The format of this field must be "<controlPlaneID>:<serviceID>". - routeIds: String[] (optional) - Filter by route IDs. The format of this field must be "<controlPlaneID:routeID>" - maxResults: Number - Maximum number of results to return (1-1000) OUTPUT: - metadata: Object - Contains totalRequests, timeRange, and applied filters - requests: Array - List of request objects with details including: - requestId: String - Unique request identifier - timestamp: String - When the request occurred - httpMethod: String - HTTP method used (GET, POST, etc.) - uri: String - Request URI path - statusCode: Number - HTTP status code of the response - consumerId: String - ID of the consumer making the request - serviceId: String - ID of the service handling the request - routeId: String - ID of the matched route - latency: Object - Response time metrics - clientIp: String - IP address of the client - and many more detailed fields... |
Manual installation
You can install the MCP server using:
Installation for