Update heartbeat for a client-side MCP server

Documentation Update the heartbeat for a previously registered client-side MCP server. This extends the TTL for the server registration.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

ID of the workspace

Body Params
string
required

The ID of the registered MCP server

Responses

400

Bad Request. Missing or invalid parameters.

401

Unauthorized. Invalid or missing authentication token.

403

Forbidden. User does not have access to the workspace.

404

Not Found. MCP server not registered or expired.

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json