Give Cursor access to the computer where your project actually runs.

Connect Cursor to RelayDesk

1. 1. Pair the target machine

   Create a RelayDesk account, install the RelayDesk agent on the Windows, macOS, or Linux machine, and pair it. The machine must be powered on, connected to the internet, and shown as online in your dashboard.

2. 2. Connect Cursor

   Use the RelayDesk Cursor integration or add a custom MCP server in Cursor. Supply the HTTPS endpoint below. Complete RelayDesk sign-in and OAuth authorization if Cursor prompts you.

3. 3. Check device discovery

   Ask Cursor to list your paired RelayDesk devices. Confirm the expected device appears before authorizing changes.

4. 4. Start with a read-only inspection

   Ask Cursor to check a project's directory, inspect a log, or read build output on that specific paired machine. Review the result before requesting a write or terminal action.

Hosted Streamable HTTP MCP endpoint

https://getrelaydesk.space/mcp

For Cursor configurations accepting an MCP JSON object:

{
  "mcpServers": {
    "relaydesk": {
      "url": "https://getrelaydesk.space/mcp"
    }
  }
}

The endpoint requires an authenticated RelayDesk connection. Do not put API secrets in a public configuration file.

View the Cursor integration source →

Example task: troubleshoot a failing build on a VM

Ask: “List my RelayDesk devices. On my test VM, inspect the project build output and tell me what failed. Do not modify files until I approve the next step.”

After inspecting the result, you can request a bounded fix and verification on that same paired device. Commands run using the permissions of the local RelayDesk agent and are subject to its safety restrictions.

What if Cursor cannot reach the machine?

• Check that the computer is online and paired in the RelayDesk dashboard.
• Reconnect the MCP server if Cursor reports expired authorization.
• Use the exact HTTPS endpoint above, not an old Vercel-domain example.
• Check which Cursor edition and connection methods support custom MCP and OAuth.

Security boundary

RelayDesk does not open an unauthenticated public shell. Access is associated with your RelayDesk account and your explicitly paired devices; protected credential and secret paths remain guarded. Only authorize actions you understand.

Read security details → · How RelayDesk works →