Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Kong Konnect Service Catalog (BYOK) — connector documentation

  • MCP endpoint: https://byok-kong-konnect-service-catalog.connectorbay.com/mcp
  • REST API: POST https://byok-kong-konnect-service-catalog.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-kong-konnect-service-catalog.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Kong Konnect Service Catalog Konnect personal or system account access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-kong-konnect-service-catalog.connectorbay.com/health · Tool schemas: https://byok-kong-konnect-service-catalog.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-kong-konnect-service-catalog · agent@connectorbay.com

What Kong Konnect Service Catalog (BYOK) is for

Kong Konnect Service Catalog (BYOK) lets an AI assistant read your own Kong Konnect Service Catalog data through the Kong Konnect Service Catalog API with a key you supply (Konnect personal or system account access token). Read-only: 11 tools (list_catalog_services, get_catalog_service, list_catalog_service_resources, list_catalog_service_scorecards, list_resource_mappings, list_integration_instances, list_scorecards, get_scorecard, list_scorecard_criteria, list_scorecard_services, list_scorecard_templates). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to us.api.konghq.com, eu.api.konghq.com, au.api.konghq.com, me.api.konghq.com, in.api.konghq.com, sg.api.konghq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Kong Konnect Service Catalog. Kong Konnect Service Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which services are in our Kong service catalog?"
  • "Who owns the orders service in the Kong catalog?"
  • "Which repositories are linked to the orders service?"
  • "How does the orders service score on our scorecards?"
  • "Which resources are mapped to which catalog services?"
  • "Which integrations are connected to our Kong service catalog?"

What it does

  • list_catalog_services: List the services in the Konnect Service Catalog with display name, description and labels.
  • get_catalog_service: Get one catalog service with description, labels and timestamps.
  • list_catalog_service_resources: List the resources (repositories, pipelines and similar) linked to one catalog service.
  • list_catalog_service_scorecards: List the scorecards that apply to one catalog service with the service's score on each.
  • list_resource_mappings: List mappings between integration resources and catalog services.
  • list_integration_instances: List configured integration instances (for example a GitHub or PagerDuty connection) with authorization state; configuration values are not returned.
  • list_scorecards: List scorecards with the overall score, the template they use and timestamps.
  • get_scorecard: Get one scorecard with its score and the criteria it evaluates.
  • list_scorecard_criteria: List the criteria of a scorecard with enabled flag, section and the evaluation result.
  • list_scorecard_services: List the catalog services a scorecard applies to with each service's score.
  • list_scorecard_templates: List the built-in scorecard templates with their criteria.

BYOK key

You bring your own Kong Konnect Service Catalog Konnect personal or system account access token (https://cloud.konghq.com/global/account/tokens/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to us.api.konghq.com, eu.api.konghq.com, au.api.konghq.com, me.api.konghq.com, in.api.konghq.com, sg.api.konghq.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Kong Konnect Service Catalog API (us.api.konghq.com, eu.api.konghq.com, au.api.konghq.com, me.api.konghq.com, in.api.konghq.com, sg.api.konghq.com) with a BYOK key; documentation: https://developer.konghq.com/api/konnect/service-catalog/v1/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Kong Konnect Service Catalog. Kong Konnect Service Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Kong Konnect Service Catalog account.

Built for: Worldwide. Languages: English.