# ReMCP [Health: Active]

**Category:** 🖥️ OS Automation  
**Repository:** https://github.com/getremcp/remcp  
**GitHub Stars:** 4  
**npm Downloads (last month):** 24003  
**Views:** 11  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/remcp-2

## Description
Securely control paired computers with ReMCP.

## Tools
Capabilities this server exposes over MCP:

- **computer_snapshot**
- **type_text**
- **browser_action**
- **keyboard**
- **pointer**
- **drag_drop**
- **wait_for_ui**
- **browser_wait**
- **screenshot_region**
- **record_screen**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "remcp": {
    "command": "npx",
    "args": ["--yes","@remcp/remcp@latest"]
  }
}
```

## Documentation

## What ReMCP does

ReMCP gives an MCP client access to paired computers through a device client and background agent. The connection is intended for computers that the user owns or administers. Once a device is paired, an AI client can invoke tools for observing the screen, interacting with a browser, entering text, sending keyboard and pointer input, moving items with drag-and-drop, waiting for interface state changes, capturing screen regions, and recording the screen.

The repository includes the device client, pairing flow, outbound agent, background service, and a local runtime package. The runtime also contains a broader collection of local tools for areas such as files, screenshots, terminal and process work, desktop UI, browser CDP, diagnostics, and document handling. The MCP tool list exposed for this listing includes `computer_snapshot`, `type_text`, `browser_action`, `keyboard`, `pointer`, `drag_drop`, `wait_for_ui`, `browser_wait`, `screenshot_region`, and `record_screen`.

## How it works

The device agent makes an outbound connection only. ReMCP does not require an inbound port, tunnel, or third-party desktop relay for the device connection. Pairing is initiated from the ReMCP connection page in an authenticated workspace. The generated pairing code is single-use and expires automatically; the exact generated command must be run on the computer being connected.

After pairing, the computer can be used from a compatible MCP host. The published plugin flow is catalog-first: users install ReMCP from the AI host, authorize it when prompted, and select or use a computer already paired to their account. ChatGPT users invoke the plugin explicitly with `@ReMCP`, while Codex exposes it through its plugin sources.

## Setup and configuration

Open ReMCP's Connect a machine page to obtain the operating-system-specific installation flow. On Windows, the PowerShell installer can run without preinstalled Node.js, npm, npx, or winget. On macOS and Linux, the shell installer can install a vetted Node.js runtime into the user's profile when necessary, without requiring `sudo`. An npm-based option is available when Node.js is already installed:

```sh
npx --yes @remcp/remcp@latest connect
```

The command-line client supports starting the agent, checking status, running diagnostics, installing or repairing the persistent user service, updating, uninstalling, and changing telemetry or local unrestricted-mode settings. Useful commands include `remcp status`, `remcp doctor`, `remcp install`, and `remcp update`.

Published setup paths cover ChatGPT and Codex, Cursor, Claude Code, Gemini CLI, and Cline. Claude Code and Claude Desktop use Claude's plugin browsing flow, subject to plugin availability and approval.

## Tools and capabilities

- Inspect a connected computer with `computer_snapshot`.
- Enter text with `type_text`.
- Perform browser operations with `browser_action` and wait for browser state with `browser_wait`.
- Send keyboard and pointer input through `keyboard` and `pointer`.
- Move items using `drag_drop`.
- Wait for interface conditions with `wait_for_ui`.
- Capture part of the display with `screenshot_region`.
- Record the screen with `record_screen`.

## Limitations and notes

The device must be paired before an MCP client can use it. Pairing codes are temporary and single-use, so commands should be generated for the intended authenticated workspace and computer. Plugin availability can depend on the host account or rollout status. ReMCP's outbound-only design avoids opening an inbound device port, but the tools still provide direct control over the paired computer; use local unrestricted mode and telemetry settings deliberately.

_Full upstream README: https://allmcps.com/mcp/remcp-2/readme_

