Can AI agents automate Kong Konnect?

Kong Konnect is automatable today through the Konnect APIs. This record is hosted Kong Konnect, not self-managed Kong Gateway. The Konnect API overview says the APIs manage Gateway configuration, analytics, and Dev Portal. The recommended credential is a bearer access token sent as Authorization. A personal access token acts as a user, lasts at most 12 months, and is limited to 10 tokens per user. A system account access token is for automation and is not a UI login. Dev Portal calls that require a developer session send a portalaccesstoken cookie. The example user call is https://global.api.konghq.com/v3/users/. Kong hosts the Konnect MCP server at https://global.mcp.konghq.com/, with regional hosts for the US, EU, AU, and IN. Authentication is a browser sign-in, a personal access token, or a system account access token. Organization administrators can disable MCP. The documented tools are search, get_schema, and execute, which discover and call Konnect API operations at runtime. Standalone MCP code mode reached general availability on May 18, 2026. The archived Kong/mcp-konnect repository is the deprecated local server and is not the current path. Connector catalogs were not opened. A separate CLI guide was not opened, though the API page says personal access tokens can also be used with CLIs. Computer-use viability is unassessed. API scores 8. MCP scores 8. API is the best path because a system account token calls Konnect without a person present, and an administrator can turn the MCP server off.

Best path today: api · Overall automatability: 8/10