How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kong MCP Servers API

The MCP Servers API from Kong — 9 operation(s) for mcp servers.

Kong MCP Servers API is one of 139 APIs that Kong publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include MCP Server. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, a GitHub repository, an API reference, authentication docs, and 1 JSON Schema.

This API exposes 13 operations across 9 paths, and defines 39 schemas. It is described by OpenAPI 3.2.0, at version 3.14.0.

Requests are made against 4 base URLs: https://global.api.konghq.com, https://us.api.konghq.com, https://eu.api.konghq.com, https://au.api.konghq.com.

13 operations 9 paths 39 schemas 1 DELETE8 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.14.0
Base URL
https://global.api.konghq.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 4

Kong MCP Servers API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (Token) (personalAccessToken). It accepts HTTP bearer tokens (Token) (systemAccountAccessToken). It accepts HTTP bearer tokens (JWT) (konnectAccessToken). It accepts HTTP bearer tokens (JWT) (serviceAccessToken). By default, every request must be authenticated.

  • personalAccessToken — The personal access token is meant to be used as an alternative to basic-auth when accessing Konnect via APIs. You can generate a Personal Access Token (PAT) f…
  • systemAccountAccessToken — The system account access token is meant for automations and integrations that are not directly associated with a human identity. You can generate a system acc…
  • konnectAccessToken — The Konnect access token is meant to be used by the Konnect dashboard and the decK CLI to authenticate with.
  • serviceAccessToken — The Service access token is meant to be used between internal services.

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 1 DELETE, 8 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

MCP Servers 13
GET
/v1/mcp-cp/{controlPlaneId}/mcp-servers
List MCP Servers by Control Plane
list-mcp-servers-by-control-plane 4 params → 200400401403
GET
/v1/mcp-cp/{controlPlaneId}/mcp-servers/{mcpServerId}
Get MCP Server by Control Plane
get-mcp-server-by-control-plane 2 params → 200400401403404
GET
/v1/mcp-cp/{controlPlaneId}/mcp-servers/{mcpServerId}/code
Get generated Python code for the MCP Server
get-mcp-server-code 2 params → 200400401403404
GET
/v1/mcp-cp/{controlPlaneId}/mcp-servers/{mcpServerId}/kong-entities
Get Kong entities for the MCP Server Gateway
get-mcp-server-kong-entities 3 params → 200400401403404
POST
/v1/mcp-cp/{controlPlaneId}/mcp-servers/{mcpServerId}/status
Report MCP Server deployment status
post-mcp-server-status 2 params body → 204400401403404
GET
/v1/mcp-cp/{controlPlaneId}/signals
Get MCP Server Signals
get-mcp-server-signals 2 params → 200304400401403
GET
/v1/mcp-servers
List all MCP Servers
list-mcp-server-configs 3 params → 200400401403
POST
/v1/mcp-servers
Create an MCP Server
create-mcp-server-config body → 201400401403409
GET
/v1/mcp-servers/{mcpServerId}
Get MCP Server
get-mcp-server-config 1 param → 200400401403404
PUT
/v1/mcp-servers/{mcpServerId}
Update MCP Server
update-mcp-server-config 1 param body → 200400401403404409
PATCH
/v1/mcp-servers/{mcpServerId}
Partially Update MCP Server
patch-mcp-server-config 1 param body → 200400401403404409
DELETE
/v1/mcp-servers/{mcpServerId}
Delete MCP Server
delete-mcp-server-config 1 param → 204400401403404
GET
/v1/mcp-servers/{mcpServerId}/status
Get MCP Server deployment status
get-mcp-server-status 1 param → 200400401403404

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are MCPServerInfo (10 properties), KongService (6 properties), PatchMCPServerRequest (6 properties), InvalidParameterMinimumLength (5 properties). Each schema is shown below with its type and property counts.

MCPServerSignals
object
The MCP server signals response.
1 property 1 required
UpdatedAt
string
An ISO-8601 timestamp representation of entity update date.
MCPServerInfo
object
10 properties 5 required
InvalidParameterChoiceItem
object
5 properties 4 required
StringFieldContainsFilter
object
Filters on the given string field value by fuzzy match.
1 property 1 required
MCPServerCodeResponse
object
1 property 1 required
MCPServerPodsStatus
object
3 properties 3 required
CursorMetaPage
object
5 properties 3 required
CreatedAt
string
An ISO-8601 timestamp representation of entity creation date.
PatchMCPServerRequest
object
6 properties
BaseError
object
standard error
5 properties 4 required
InvalidParameters
array
invalid parameters
ListMCPServersResponse
object
2 properties 2 required
BadRequestError
InvalidParameterMinimumLength
object
5 properties 4 required
MCPServerStatusResponse
object
1 property 1 required
ForbiddenError
UnauthorizedError
NotFoundError
MCPServerSignal
A single signal envelope containing exactly one typed capability signal.
InvalidParameterDependentItem
object
5 properties 4 required
InvalidRules
string
invalid parameters rules
MCPCapabilitiesMap
object
Map of capability name - capability request fields. Example: { "mcp": { "version": "v1", "offset": "5" } }
1 property
InvalidParameterMaximumLength
object
5 properties 4 required
MCPServerSignalV1
object
Signal notifying the client that the MCP control plane config has changed.
3 properties 3 required
CursorMeta
object
Pagination metadata.
1 property 1 required
ConflictError
KongService
object
6 properties 5 required
ListMCPServersCPInfoResponse
object
2 properties 2 required
KongEntitiesResponse
object
2 properties 2 required
MCPServerCPInfo
MCPCapabilityRequest
object
2 properties 1 required
MCPServerStatusRequest
array
List of per-version deployment statuses for the MCP server.
KongRoute
object
5 properties 3 required
UpdateMCPServerRequest
object
5 properties 1 required
MCPServerVersionStatus
object
4 properties 4 required
InvalidParameterStandard
object
4 properties 2 required
ContainerSpec
object
1 property
CreateMCPServerRequest
object
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-mcp-servers-api-openapi.yml Raw ↑

Other APIs Kong publishes across the network.

Kong Gateway
Kong AI Gateway
Kong Agent Gateway
Kong MCP Registry
Kong Context Mesh
Kong Mesh
Kong Insomnia
Kong Add-Ons API
Kong API Attributes API
Kong API Documentation API
Kong API Image API
Kong API Implementation API
Where this information came from

This is an independent, third-party profile of Kong MCP Servers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.