The Konnect MCP server exposes 23 tools with explicit schemas and descriptions, but exhibits significant quality gaps. All tools have descriptions and input schemas visible in the code, but many descriptions lack sufficient detail to guide LLM selection. Parameter descriptions are present but often minimal (e.g., 'The ID of the control plane' with no context about format or how to obtain it). Critical issues: (1) Many object-type parameters lack nested schema definitions (e.g., 'service', 'route', 'consumer', 'basicAuth' are typed as 'object' with no properties documented). (2) Error handling and recovery guidance are absent from tool descriptions. (3) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications. (4) Descriptions for CRUD operations don't explain prerequisites, side effects, or when to use one over another. Average per-tool score: 52 (range 35 - 65), placing this server in the 'fair to poor' range for production use.
Create a new basic-auth credential in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - consumerId (optional): Consumer ID to associate the basic-auth credential - basicAuth (required): Basic-auth credential configuration - username (required): Username for the credential - password (required): Password for the credential - tags (optional): An array of tags for the credential Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumerId": "84a73fb8-50fc-44a7-a4d5-aa17728ee83f", "basicAuth": { "username": "johndoe", "password": "securepassword123", "tags": ["production"] } } Response will include: - The created basic-auth credential object
Create a new consumer in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - consumer (required): Consumer configuration object - username (optional): The unique username of the Consumer - custom_id (optional): A custom identifier for the Consumer - tags (optional): An array of tags for the Consumer Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumer": { "username": "bob-the-builder", "custom_id": "4200", "tags": ["silver-tier"] } } Response will include: - The created consumer object
Create a new route in a Konnect control plane.
Create a new service in a Konnect control plane.
Object-type parameters lack nested schema definitions. CreateService, UpdateService, CreateRoute, UpdateRoute, CreateConsumer, UpdateConsumer, CreateBasicAuth, UpdateBasicAuth all accept 'service', 'route', 'consumer', 'basicAuth' objects typed as 'object' with no 'properties' defined. This prevents LLMs from knowing what fields are required or optional.
Tool annotations missing. No tools declare readOnlyHint, destructiveHint, or idempotentHint in their definitions. Risk classification (READ_ONLY, WRITE, DESTRUCTIVE) is noted in the provided metadata but not exposed to the MCP protocol, so LLMs cannot see which operations are safe to retry or which are destructive.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 46 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 11 | - | v1 |
Delete a basic-auth credential from a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - basicAuthId (required): ID of the basic-auth credential - consumerId (optional): Consumer ID associated with the credential Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "basicAuthId": "b2f34145-0343-41a4-9602-4c69dec2f269" } Response will include: - Success confirmation
Delete a consumer from a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - consumerId (required): The ID or username of the consumer to delete Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumerId": "8a388226-80e8-4027-a486-25e4f7db5d21" } Response will include: - Success confirmation
Delete a route from a Konnect control plane.
Delete a service from a Konnect control plane.
Fetch a specific basic-auth credential from a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - basicAuthId (required): ID of the basic-auth credential - consumerId (optional): Consumer ID associated with the credential Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "basicAuthId": "b2f34145-0343-41a4-9602-4c69dec2f269" } Response will include: - The basic-auth credential object with all its properties
Fetch a specific consumer from a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - consumerId (required): The ID or username of the consumer to fetch Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumerId": "8a388226-80e8-4027-a486-25e4f7db5d21" } Response will include: - The consumer object with all its properties
Fetch a specific route from a Konnect control plane.
Fetch a specific service from a Konnect control plane.
List basic-auth credentials in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane to list basic-auth credentials from - consumerId (optional): Filter basic-auth credentials by consumer ID - tags (optional): Tags to filter basic-auth credentials by. Use comma (,) for AND, forward slash (/) for OR Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumerId": "84a73fb8-50fc-44a7-a4d5-aa17728ee83f", "tags": "production" } Response will include: - List of basic-auth credentials in the control plane - Credential details like username, consumer association, etc. - Metadata about the credentials
List consumers in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane to list consumers from - tags (optional): Tags to filter consumers by. Use comma (,) for AND, forward slash (/) for OR Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "tags": "silver-tier" } Response will include: - List of consumers in the control plane - Consumer details like username, custom_id, etc. - Metadata about the consumers
List the number of control planes in a Konnect account. It takes one argument - region (str, optional): the region (default is us) - pageNumber (number, optional) (default 1) - pageSize (number, optional) (default 10)
List routes in a Konnect control plane.
List all searchable entity types in Konnect. Parameters: - region (optional): Konnect region (default is "us") Response will include: - List of searchable entity types - Details about each type including name, description, searchable attributes, etc. - Regions where each entity type is available
List services in a Konnect control plane.
Search for entities in Konnect using a query string. Parameters: - q (required): The query that defines the search criteria (e.g., "name:\"John Smith\"") - region (optional): Konnect region (default is "us") - pageSize (optional): Maximum number of items per page (default is 10) - pageAfter (optional): Token for pagination to request the next page Example usage: { "q": "name:\"API Gateway\"", "region": "us", "pageSize": 20 } Response will include: - List of matched Konnect entities - Entity details like id, type, name, description, etc. - Pagination metadata
Update an existing basic-auth credential in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - basicAuthId (required): ID of the basic-auth credential - consumerId (optional): Consumer ID associated with the credential - basicAuth (required): Updated basic-auth credential configuration - username (optional): New username - password (optional): New password - tags (optional): Updated tags Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "basicAuthId": "b2f34145-0343-41a4-9602-4c69dec2f269", "basicAuth": { "password": "newpassword456", "tags": ["production", "updated"] } } Response will include: - The updated basic-auth credential object
Update an existing consumer in a Konnect control plane. Parameters: - controlPlaneId (required): The ID of the control plane - consumerId (required): The ID or username of the consumer to update - consumer (required): Updated consumer configuration Example usage: { "controlPlaneId": "9524ec7d-36d9-465d-a8c5-83a3c9390458", "consumerId": "8a388226-80e8-4027-a486-25e4f7db5d21", "consumer": { "username": "new-username", "tags": ["gold-tier"] } } Response will include: - The updated consumer object
Update an existing route in a Konnect control plane.
Update an existing service in a Konnect control plane.
Error handling and recovery guidance absent from descriptions. No tool description explains what errors are likely, what they mean, or how to recover. E.g., CreateService doesn't mention 'If validation fails, call ListSearchTypes first to see available configuration options' or clarify whether the error is retryable.
Parameter descriptions too generic or incomplete. Many critical params have minimal descriptions: 'The ID of the control plane' doesn't explain how to obtain it if unknown, or confirm its format. 'Service configuration' is vague, the LLM must infer what fields belong in the object.
No output schema documentation. Tool descriptions do not explain what fields are returned, their types, or how to chain results to downstream tools. Users/LLMs must infer the response structure from the implementation.
Natural identifiers not supported. Parameters like 'controlPlaneId', 'serviceId', 'routeId', 'consumerId' require opaque system IDs. No tool accepts human-readable names (e.g., 'controlPlane by name', 'service by name'). Users typically know names, not IDs, forcing extra lookup calls.
Pagination support inconsistent and incomplete. ListServices, ListRoutes, ListConsumers, ListBasicAuth accept pageSize and pageNumber (or pageOffset), but tool descriptions don't clarify whether a total count is returned, how to detect the last page, or what happens if pageNumber exceeds available pages.
Create/Update descriptions don't distinguish prerequisites or side effects. 'Update an existing service' is vague, what happens if I update a service in use? Are there validation rules? Does it require approval? What fields are immutable?