MCP setup

Technical connection details for Captain Relay's remote MCP server.

Endpoint

https://mcp.captainrelay.com/mcp

Transport and authentication

Remote Streamable HTTP MCP transport.
OAuth authentication through Captain Relay.
Bearer access is scoped to the signed-in account.
Device ownership and execution policy are enforced server-side.

Recommended client flow

Connect the production MCP endpoint.
Complete the OAuth sign-in flow.
Call list_devices before operating a computer unless you already have an exact device ID.
Call get_device to discover the exact tools exposed by that device.
Use the narrowest applicable tool and arguments.
If Captain Relay returns an approval ID, wait for the human decision and retrieve that approval rather than replaying the original action.

Long-running work

Use persistent device jobs for work likely to outlive a normal request, then inspect progress with the returned job ID.

Privacy

Remote computer content can contain personal or confidential information. Request only the data needed for the user's task, and do not expose credentials, tokens or unrelated files.

Support

Captain Relay Support