MCP Servers
Get MCP Server 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.
get/v1/mcp-cp/{controlPlaneId}/signals
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"
}
]
}