---
title: "Get MCP Server Signals"
method: GET
path: "/v1/mcp-cp/{controlPlaneId}/signals"
tags: ["MCP Servers"]
---

# Get MCP Server Signals

`GET /v1/mcp-cp/{controlPlaneId}/signals`

**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.

## Query parameters

- `capabilities` MCPCapabilitiesMap — Map of capability name -> capability request fields. Example: { "mcp": { "version": "v1", "offset": "5" } }
  - `mcp` MCPCapabilityRequest
    - `version` string, required — The version of the capability schema (e.g., v1).
    - `offset` string — The version of the control plane known by the client.

## Response `200`

The MCP server signals response.

- MCPServerSignals — The MCP server signals response.
  - `signals` MCPServerSignal[], required — A list of signals for the MCP server.
    - `type` 'mcp', required
    - `version` string, required — The current version of the MCP control plane.
    - `offset` string, required — The offset for the MCP signal.

## Other responses

- `304` — No signals available (client is up to date)
- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden

---

[API](https://skmtc.net/kong/apis/konnect-api-go-sdk.md) · [All operations](https://skmtc.net/kong/apis/konnect-api-go-sdk/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kong/konnect-api-go-sdk/revisions/0aee8d012787/schema)