Support

Troubleshooting.

Check the layer that is failing: sign-in, pairing, the local agent, or MCP authorization.

Still stuck? Write to support [at] remcp [dot] site — the address is assembled in your browser, not published in the page.

Sign-in does not open

Use Continue with Google or Continue with GitHub. ReMCP does not use email/password sign-in on the hosted site. If a popup is blocked, allow popups for remcp.site and try again.

The remcp command is missing

After installation, pair the computer from the signed-in workspace. The public install command alone does not pair a device.

Pairing command expired

Open the workspace and generate a new command. Each pairing command contains a one-time code and expires automatically.

Device shows offline

Confirm the user service is running and outbound HTTPS/WSS access to remcp.site is allowed. Re-pair only if the device credential was revoked or the local pairing state was removed.

OAuth does not complete

Return to the authorization page, sign in with the intended ReMCP account, review the requested scopes, and choose Authorize ReMCP Access.

MCP tool cannot run

Confirm the target device is online. A device tool needs the current ReMCP device id; clients can obtain it with list_devices.

Update or repair

If the CLI is paired but its background service is missing, run remcp install.