Support

Troubleshoot ReMCP.

Most connection failures fall into one of three layers: account authentication, device pairing, or the local device agent.

Device shows offline

Verify the ReMCP agent service is running and outbound HTTPS/WSS access to remcp.delio24.com is allowed. Re-pair the device if its credential was revoked.

OAuth does not complete

Return to the authorization screen, sign in to the intended ReMCP account, review the requested access, and choose Authorize ReMCP access.

MCP tool cannot run

Confirm the target computer is online and use list_devices to obtain its current device id. Device tools require that id.

Pairing code expired

Generate a new pairing command from the workspace. Pairing codes are intentionally short-lived and single-use.

Need deployment help?

For a self-hosted deployment, contact the operator who provisioned your ReMCP instance and include the affected layer: sign-in, pairing, agent connectivity, or MCP authorization.