Get Mcp Harnesses

Every harness the caller has connected to Traversal MCP from.

The organization and user are always the caller's. Harnesses come from self-reported client names, and unrecognized or missing names read as Other.

get/user/mcp/harnesses

Response

Successful Response

harnessesMcpHarness[] required

Each harness once, in McpHarness order. All time.

stream_cursorinteger nullable required

Highest seq on this user's harness stream. Null when nothing was published. Pass it as the stream_data cursor when opening the websocket. Each event carries the raw client_name; refetch this endpoint for harness labels.

Changes

Changed in 2 of the 63 revisions of this API.2

Sep 30, 20264fa2a4911e011See the full diff
- ○
  added the required property to the response with the status
  response-required-property-added
Sep 28, 2026ff08ffe40f1a1See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 63 revisions, 9 have no diff computed.

Full history