Signaling APIs

Get MCP Server Signals

Changed on

Pre-release Endpoint This endpoint is currently in beta and is subject to change.

Client-initiated signals fetch with long-polling capabilities. The client supplies capabilities as a deepObject query parameter:

  • Keys are capability names (e.g. mcp)
  • Values contain the capability request fields (version)

Example:

GET /mcp-cp/{controlPlaneId}/signals?capabilities[mcp][version]=5

The CP responds with a JSON payload containing zero or more signals that the client should process. If no signals are available, the CP responds with HTTP 304 Not Modified.

get/v1/mcp-cp/{controlPlaneId}/signals

Request

  • Base URL: https://global.api.konghq.com
  • URL: https://global.api.konghq.com/v1/mcp-cp/{controlPlaneId}/signals
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer
    • HTTP bearer

Query parameters

Capability requests as a deepObject map.

  • Keys are capability names (e.g. mcp).
  • Values contain the capability request fields (version).

Response

The MCP server signals response.

Example response

{
  "signals": [
    {
      "type": "mcp",
      "version": "v1",
      "offset": "6"
    }
  ]
}

Changes

  • 7aab863a6daaRevision changes
    • breaking

      added to the / response property oneOf list for the response status

    • warning

      added the new key_invalid enum value to the ////// response property for the response status

    • warning

      added the new unique enum value to the ////// response property for the response status

  • de79e1192f11Revision changes
    • info

      api tag Signaling APIs added

    • info

      api tag MCP Servers removed