Documentation

Install and pair ReMCP.

Install the CLI first. Pairing happens from the signed-in workspace, which generates the real one-time command for your computer.

Your workspace

After signing in, Overview shows call volume, success rate, duration and tool usage. Activity lets you filter completed calls by period, tool, device and result. Statistics start from the first call after analytics is enabled; older activity is not reconstructed.

Use Connect a machine to generate a command and watch its expiration timer. The page detects when the code is claimed. Requesting the command again returns the same code until it expires. Devices shows online status, supports search and immediately disconnects machines when you revoke access.

Requirements

Node.js 22.5 or newer. The computer needs outbound HTTPS/WSS access to remcp.site. No inbound device port is required.

1. Install the CLI

npm install --global @remcp/remcp@latest

This installs the remcp command. It does not pair a computer and does not contain a placeholder code.

2. Pair a computer

Open the ReMCP workspace, continue with Google or GitHub, and choose Generate pairing command. Run that exact generated command on the computer you want to pair.

Use the generated command.

Pairing codes are short-lived and single-use. Do not type a made-up code or reuse an expired command.

3. Verify

remcp --version
remcp status

status shows the installed CLI version, pairing state and server health.

4. Add the MCP endpoint

https://remcp.site/mcp

Add this endpoint to your MCP client and use OAuth when prompted. ReMCP uses authorization code flow with PKCE and refresh-token rotation.

Update

remcp update

Updates the installed ReMCP CLI and compatible local runtime, then restarts the user service when present.

Service commands

remcp status
remcp doctor
remcp install
remcp start

install installs or repairs the background user service for an already paired computer. start runs the agent in the foreground.

Uninstall

remcp uninstall

Removes the background service. To also remove globally installed ReMCP packages:

remcp uninstall --purge

Connection model

The device agent opens an outbound secure WebSocket connection to the relay. MCP clients connect to the HTTPS MCP endpoint through OAuth. Only devices paired to the signed-in account are exposed to that account.

Self-hosting

The server can be self-hosted with Docker. Keep it behind TLS, persist its data volume, and proxy WebSocket upgrades for the device-agent route. See the repository README for deployment variables.