Your computer. Your tools. One secure MCP connection.
Website · Plugins · Docs · Tool reference · Security · Privacy · Support
ReMCP connects a computer you own or administer to ChatGPT & Codex, Cursor, Claude Code, Gemini CLI, Kiro, Cline, or another MCP client. The device agent makes an outbound connection only — no inbound port, no tunnel, no third-party desktop relay. This repository contains the public device client/runtime, portable Agent Plugin metadata, the Gemini CLI extension manifest, official MCP Registry metadata, and the host-specific OpenAI and Anthropic plugin packaging.
| Package | What it is |
|---|---|
@remcp/remcp |
The device client: pairing, the outbound agent, the background service, and the usage-metrics switch. |
@remcp/runtime |
The first-party local runtime: 84 MCP tools for files, images, binary transfer, archives, screenshots, search, terminal/process work, native desktop UI, loopback browser CDP, diagnostics, lightweight documents, and narrowly scoped runtime preferences, with two direct dependencies. |
Open ReMCP → Connect a machine. The page detects the computer's operating system and shows the correct one-command flow.
Windows PowerShell — no preinstalled Node.js, npm, npx, or winget required:
irm https://remcp.site/i | iexReMCP keeps its Windows runtime privately under %LOCALAPPDATA%\ReMCP; it does not install Node.js
globally or add the private runtime directory to the system PATH.
macOS / Linux — no Node.js or npm needed beforehand:
curl -fsS https://remcp.site/i.sh | shThe installer asks before installing a vetted, checksum-verified Node.js runtime into your user
profile when needed. It then runs the production-compatible ReMCP version. No sudo required.
The downloaded script is parsed in full before any installation actions begin.
If Node.js is already installed, the advanced npm shortcut is npx --yes @remcp/remcp@latest connect.
For inspecting the script before running it, open https://remcp.site/i.sh in your browser.
The browser can also generate a one-time pairing command. Run that exact command on the computer you want to connect; it installs the runtime and registers the background service.
Pairing codes are generated in the authenticated workspace, expire automatically, and are single-use. Do not invent or reuse a code from documentation.
| Command | Purpose |
|---|---|
remcp start |
Start the device agent when no managed background service is already running |
remcp status |
Show device, client/runtime versions, managed-agent state, update consistency and server reachability as JSON |
remcp doctor |
Status plus a real local-runtime handshake and filesystem diagnostics |
remcp install |
Install or repair the persistent user service |
remcp update |
Update the client and runtime, then restart the service |
remcp uninstall |
Stop and remove the user service |
remcp uninstall --purge |
Remove the service and the global packages |
remcp telemetry [status|on|off] |
Show or change usage metrics for the client and the runtime |
remcp godmode [status|on|off] |
Show or change this computer's local unrestricted mode |
remcp --version |
Print the installed client version |
For users, ReMCP is catalog-first:
Install from your AI host → sign in to ReMCP → use your paired computers.
You do not need to paste an MCP server URL, edit a manifest, clone this repository, or configure a local path just to use the published plugin.
Shareable install guides:
- ChatGPT plugin (direct): https://chatgpt.com/plugins/plugin_asdk_app_6aaaba1295a4819195a4987e18e43428
- ChatGPT & Codex guide: https://remcp.site/install/chatgpt
- Claude Code: https://remcp.site/install/claude
ChatGPT and Codex share OpenAI's public plugin directory.
- Open the published ReMCP plugin listing.
- Check that ReMCP is available for your ChatGPT account or workspace.
- Choose Install plugin.
- If prompted, choose Connect and complete ReMCP OAuth.
- In ChatGPT, use @ReMCP when you want to invoke it explicitly. In Codex, use Sources → Use plugins → ReMCP.
If ReMCP is not visible yet, the listing or rollout is not available to that account. There is no manual MCP endpoint an ordinary plugin user needs to configure while waiting.
ReMCP was submitted through Claude Platform on September 18, 2026 and currently shows Submitted and pending review.
After approval:
- Open https://claude.com/plugins. In Claude or Claude Desktop, you can also use Customize → Plugins → + → Browse plugins.
- Search for ReMCP and confirm it supports Claude Code.
- Choose Install.
- Complete ReMCP authorization if Claude asks you to connect.
- Ask Claude Code to use ReMCP on a computer already paired to your account.
While the listing is under review, ordinary users do not need to add a marketplace, clone this repository, or paste an MCP endpoint. Developer and reviewer workflows live in the technical guide.
Start with Plugin overview →.
ReMCP publishes host-native metadata for coding agents plus directory records for MCP discovery:
| Host / directory | User path | Status |
|---|---|---|
| Cursor | Add https://remcp.site/mcp as a remote MCP server in Cursor settings, then authorize. |
manual MCP setup |
| Gemini CLI | Install from the Extension Gallery when indexed, or run gemini extensions install https://github.com/getremcp/remcp. |
gallery discovery enabled |
| VS Code | Configure the remote MCP endpoint in an MCP-capable client. | manual MCP setup |
| Kiro Powers | Import https://github.com/getremcp/remcp from Add Custom Power → Import power from GitHub while the curated listing is reviewed. |
submitted |
| Cline | Restored PR #347 (original #125) | Open, awaiting external review; original fork was deleted 26 Oct 2026 |
| Kilo Marketplace | Restored PR #498 (original #480) | Open, awaiting external review; original fork was deleted 26 Oct 2026 |
| Docker MCP Registry | Restored PR #6171 (original #5159) | Open, awaiting external review; original fork was deleted 26 Oct 2026 |
| MCP Find | PR #316 | Submitted 24 Oct 2026; fork-safe validation pending and directory review required |
| MCP Server Finder | Free directory | Repo checked absent 25 Oct 2026; editorial email submission sent 25 Oct, review pending |
| FindMCP | Free submission portal | ReMCP submission ID 321 accepted 25 Oct 2026; review pending |
| Few Servers | Free editorial form | 25 Oct 2026: listing/claim request emailed to editor; external review pending; not verified listed |
| AgenticSkills | Free MCP server submission | Accepted for weekly editorial review 25 Oct 2026; public listing not yet confirmed |
| MCP Harbor | Free submission portal | Docsy and ReMCP submitted 24 Oct 2026; ReMCP awaiting external review/daily indexing, not yet verified listed |
| Plug and Ship | Public ReMCP page | Free launch accepted 24 Oct 2026; daily board scheduled 12 Nov 2026, not yet launched |
| LibHunt | Public ReMCP listing | Published and verified HTTP 200 on 24 Oct 2026; free submission automatically approved |
| Ext Ops Panel | Public ReMCP MCP profile | Auto-indexed from official MCP Registry, verified public 25 Oct 2026; not host endorsement |
| Walnut World | Public ReMCP source page | GitHub-source listing published 25 Oct 2026, independently verified in Chrome; ownership unclaimed |
| MCPRepository | ReMCP listing | Existing listing confirmed via duplicate-detection API and HTTP 200 on 24 Oct 2026 |
| MCP Market | Public ReMCP listing | publicly indexed; existing-listing confirmation 24 Oct 2026 |
| Punkpeye Awesome MCP Servers | Merged PR #14685 | verified merged 18 Oct 2026; public source-install catalog |
| AI Anytime Awesome MCP Servers | ReMCP listing PR #314 | merged 24 Oct 2026; listed in the public GitHub directory |
| Sagargupta Awesome MCP Servers | ReMCP listing PR #214 | merged 24 Oct 2026; listed in the public GitHub directory |
| TensorBlock Awesome MCP Servers | Merged PR #4495 | accepted 25 Oct 2026 into upstream catalog; public API sync may lag |
| VoltAgent Official MCP Servers | PR #56 | Closed by upstream maintainer 25 Oct 2026, not merged |
| Awesome Public MCP Servers | PR #84 | submitted 25 Oct 2026; explicitly discloses mutating paired-device tools, review pending |
| Awesome MCP Tools | PR #21 | submitted 25 Oct 2026; remote OAuth computer access tools, review pending |
| PenguinMiaou Awesome Claude Code Plugins | PR #11 | submitted 25 Oct 2026; community review pending, not Anthropic endorsement |
| itgoyo Awesome Claude Code | PR #20 | submitted 25 Oct 2026; community review pending, not Anthropic endorsement |
| Claude Plugins Radar | PR #4 | submitted 25 Oct 2026; community review pending, not Anthropic endorsement |
| ClaudeMods | Editorial issue #35 | Submitted 25 Oct 2026; bot/editor review pending |
| Habito Awesome MCP Servers | PR #298 | submitted 25 Oct 2026; external curator review pending, no platform endorsement |
| DhanushNehru Awesome MCP Servers | PR #128 | submitted 25 Oct 2026; external curator review pending, no platform endorsement |
| Awesome Productivity MCP Servers | PR #48 | submitted 25 Oct 2026; external curator review pending, no platform endorsement |
| WunderCorp Awesome MCP | PR #155 | submitted 25 Oct 2026; external curator review pending, no platform endorsement |
| Awesome Codex | PR #32 | submitted 25 Oct 2026; awaiting independent review |
| Awesome AI Coding Tools | PR #8 | submitted 25 Oct 2026; awaiting independent review |
| Awesome MCP Collection | PR #73 | submitted 25 Oct 2026; awaiting independent review |
| Albertchamberlain Awesome-MCP | PR #117 | Submitted 25 Oct 2026; independent review pending, not published |
| Epistates Awesome MCP DevTools | PR #24 | Submitted 25 Oct 2026; independent review pending, not published |
| Backblaze Awesome Agent Infrastructure | PR #44 | Submitted 25 Oct 2026; awaiting maintainer review |
| Awesome DevOps AI | PR #78 | Submitted 25 Oct 2026; awaiting maintainer review |
| awesome-mcp.tools (adw0rd) | Existing upstream listing | Confirmed in public main 25 Oct 2026, canonical getremcp/remcp URL; no duplicate PR |
| TrackMCP | Submission form | Accepted 25 Oct 2026, email confirmation/review pending; not yet verified publicly listed |
| Best-of MCP Servers | Restored PR #575 (original #562) | Open, awaiting external review; original fork was deleted 26 Oct 2026 |
| mcpHQ Awesome MCP Servers | Submission PR | open, awaiting maintainer review |
| ToolSDK MCP Registry | Merged PR #1019 | merged 25 Oct 2026 |
| MobinX Awesome MCP List | Submission PR | open, awaiting maintainer review |
| Ever Works Awesome MCP Servers | PR #213 | Submitted 24 Oct 2026; full ReMCP detail page awaiting catalog review |
| Awesome Claude Code Plugins | PR #822 | Submitted 24 Oct 2026; external community review pending |
| Awesome Gemini CLI Extensions | ReMCP PR #95 | Submitted 24 Oct 2026; review pending |
| AlexMili Awesome MCP | Merged ReMCP PR #327 | Published in upstream README; merged 24 Oct 2026, commit 158a622; verified 25 Oct |
| Collabnix Awesome MCP Lists | PR #265 | Submitted 24 Oct 2026; pending third-party review |
| mctrinh Awesome MCP Servers | PR #180 | Submitted 24 Oct 2026; pending review |
| Awesome MCP ZH | PR #839 | Submitted 24 Oct 2026; Chinese-language entry pending review |
| Wagner Awesome DevOps MCP Servers | PR #113 | submitted 24 Oct 2026; external review pending |
| Awesome DevOps MCP Servers | PR #381 | submitted 24 Oct 2026; external review pending |
| MindPal Awesome Remote MCP Servers | PR #231 | submitted 24 Oct 2026; awaiting remote catalog review |
| YuzeHao Awesome MCP Servers | PR #719 | submitted 24 Oct 2026; review pending |
| Awesome Remote MCP Servers (jaw9c) | PR #1637 | submitted 24 Oct 2026; external review pending |
| Brethof AI Awesome MCP Servers | ReMCP PR #54 | submitted, awaiting review |
| Docker MCP Registry | ReMCP PR #5159 | submitted, review required |
| CheckMCP | Free audit submission | received 24 Oct 2026; pending public audit/listing |
| MCP Index | Submission portal | received 24 Oct 2026; pending review |
| ProMCP | Free submission | accepted 24 Oct 2026; pending manual review |
| MCP Servers | Free submission | accepted 24 Oct 2026; pending review |
| Launch MCP | Submission status | pending after verified non-duplicate submission 24 Oct 2026; not yet published |
| MCPizy | Free ReMCP submission | Received 25 Oct 2026 (ID web_mvnk77mz_gwrdi7); independent review pending |
| MCPfinder | Submission portal | submitted through free tier 24 Oct 2026; approval pending |
| Kilo Marketplace | PR #480 | submitted, awaiting independent review |
| MCP.Directory | Publisher submission | direct ReMCP GitHub URL submitted successfully 24 Oct 2026; approval not verified |
| Smithery (retired) | Smithery shutdown notice; the former ReMCP listing returns 404. | unavailable since 31 Oct 2026 |
| Glama | Open the ownership-verified connector at https://glama.ai/mcp/connectors/site.remcp/re-mcp. | verified / healthy |
| Awesome Remote MCP Servers | Open the community directory; ReMCP is listed under Developer Tools after PR #435 was merged. | listed |
| Official MCP Registry | Search for io.github.getremcp/remcp; GitHub resolves the project release URL antonbaider/remcp to the transferred getremcp repository, so this Registry namespace remains the active identity. |
published |
The same ReMCP OAuth account and paired computers sit behind every route. Marketplace and directory surfaces change discovery; they do not create separate ReMCP backends.
Distribution manifests, direct install commands, and review links are documented in PLUGINS.md → and DISTRIBUTION.md →.
Host-specific manifests, MCP configuration, validation commands, submission artifacts, and local development workflows remain documented separately:
The OpenAI files and Claude files deliberately do not overwrite each other. Release checks fail if either host-specific contract drifts from the shared ReMCP version or production endpoint.
For source-linked developer documentation alongside local computer access, combine ReMCP with the separate Docsy AI / MCP Plugin. Docsy exposes five read-only public documentation tools (resolve-library-id, list-library-versions, query-docs, search, fetch) through https://docsy.remcp.site/mcp/registry and requires its own OAuth 2.1 authorization. ReMCP's device tools and Docsy's documentation tools remain separate services.
@remcp/runtime is a clean-room MCP server written for ReMCP. It is not a fork of, and shares no code
with, DesktopCommanderMCP or any other MCP
server.
87 granular device operations, 10 hosted production definitions. Current production advertises 8 device-facing façade tools plus 2 account/fleet tools, all model-visible. If custom widgets are explicitly re-enabled, discovery expands to 15 definitions by adding 5 app-only UI helpers. See the generated full tool reference for every current façade and its operation list.
Device runtime surface:
| Area | Tools |
|---|---|
| Read | read_file, read_files (glob), read_multiple_files, read_image, read_binary, list_directory, get_file_info, hash_file, diff_files |
| Write / edit | write_file, write_files (bulk), write_binary, apply_patch, set_permissions, edit_block, replace_lines, replace_in_files |
| Organise | create_directory (bulk), move_file, copy_file, copy_paths, move_paths, move_to_trash, create_archive, extract_archive |
| Delete | delete_path, delete_paths |
| Transfer | read_binary and write_binary move any file in base64 chunks both ways; create_archive and extract_archive move whole trees |
| Screen | take_screenshot returns the desktop as an image |
| Search | start_search, get_more_search_results, stop_search, list_searches |
| Processes | start_process, read_process_output, wait_for_process_output, interact_with_process, force_terminate, list_sessions, list_processes, kill_process |
| Runtime | get_system_info, get_runtime_info, get_runtime_stats, set_config_value |
| Computer use | computer_snapshot, computer_action, list_windows, window_action, launch_app, ui_snapshot, ui_find, ui_action, type_text, keyboard, pointer, drag_drop, scroll, wait_for_ui, clipboard, display_inventory, screenshot_region, open_path, reveal_path, notification |
| Browser | browser_tabs, browser_navigate, browser_snapshot, browser_find, browser_action, browser_wait, browser_evaluate |
| Diagnostics | service, event_log, network, installed_apps, environment, audio, power_action, record_screen |
| Documents | read_document, edit_spreadsheet, edit_document, pdf_action |
The hosted ReMCP endpoint currently advertises 10 model-visible tools with REMCP_CUSTOM_WIDGETS_ENABLED=false; no app-only render/save/refresh helpers or structuredContent.preview references are exposed. The compact surface routes to all 87 granular runtime operations, and 101 compatibility names remain callable for cached clients without inflating discovery for new models. If widgets are explicitly re-enabled later, the hosted catalog expands to 15 definitions and 106 compatibility names. Each online device returned by list_devices reports its live supported subset, and unavailable operations fail closed.
ReMCP publishes selection-oriented descriptions and ships the same decision tree in its operator skill:
native Accessibility/UI Automation → browser DOM/CDP → OCR → coordinates
- Start unfamiliar desktop work with
computer_snapshot; useui_snapshot/ui_find/ui_actionfor native apps. - For Chromium page content use
browser_navigate action=new_tabwhen needed, thenbrowser_snapshot/browser_find/browser_action/browser_waitinstead of desktop coordinates. - Use
type_textfor normal Unicode text in native/focused controls,browser_actionfor Chromium page DOM text, andkeyboardfor shortcuts/navigation keys. - Use
pointeronly when semantic actions cannot express the task; prefer element ids fordrag_drop. GNOME Wayland drag uses the consent-backed Remote Desktop portal rather than unreliable XTEST drag. - Use
wait_for_ui/browser_waitinstead of fixed sleeps. - Use
screenshot_regionfor targeted visual proof andrecord_screenonly for motion/timing. - Use structured document tools instead of automating Office when the request is about file content.
All 40 computer/browser/diagnostic/document tools declare closed top-level input schemas, parameter descriptions, structured output schemas, and MCP read-only/destructive/idempo 8BD0 tent/open-world hints.
Why the tool list looks different from other computer-control servers. Security-sensitive configuration remains deliberately narrow, and everything else the alternatives can do has an equivalent here — usually more than one:
| Not included | Why |
|---|---|
| Bundled browser/document rendering stacks | ReMCP supports lightweight DOCX/XLSX/PDF operations but deliberately uses OOXML and existing system PDF utilities instead of bundling Puppeteer, sharp, exceljs, or Chromium. |
| Broad configuration mutation | set_config_value can change only telemetry and context/output preferences. Access roots, blocked commands, command policy, shell, write limit and unrestricted mode stay local to the computer. |
URL fetching in read_file |
It is a server-side request forgery surface. The runtime reads your computer, not the internet. |
What ReMCP adds beyond the usual set: image reads and screenshots that any MCP client can
display, binary transfer in both directions, archive create/extract, wait_for_process_output instead
of polling, line-range replacement, project-wide replace, unified diffs, checksums, trash instead of
deletion, and host resource reporting.
Nothing is gated. There is no approval prompt, no "are you sure", and no mandatory dry run: a tool
call executes with the full rights of the account running the agent — the same trust model as SSH.
Writes replace by default and moves/copies replace the destination. The catastrophic-command
guardrail defaults to block (a matching command is refused before it runs); an operator may choose
warn or allow.
Files are never written to a local history log, so tool arguments and output are not recorded there.
- No per-call approval contour. ReMCP does not add a confirmation dialog before each tool call.
The local runtime's configured roots, command blocklist and command policy still apply, as do the
operating-system permissions of the account running the agent. Within those boundaries,
start_processcan operate services, packages, databases, containers,sudo, git, and other local tools. - Full transfer in both directions.
read_binary/write_binarymove any file,create_archiveandextract_archivemove whole trees, andtake_screenshotshows the desktop. - Optional hardening, explicit security boundaries.
remcp godmode onlifts the roots, the blocklist and the command guardrail for one computer — and only a person at that computer can turn it on; no MCP tool accepts it.allowedRootsandblockedCommandsare empty until an operator configures them.dangerousCommandsdefaults toblock: a matching catastrophic command is refused before it runs;warnlets it run with an advisory note andallowsilences even that. The runtime refuses to start — loudly — ifruntime.jsoncannot be parsed, so configured safety boundaries are never silently dropped. - Crash-resistant. A bad shell, a closed stdin, or a 40 MB line cannot take the runtime down; the agent restarts it if it exits, so a device recovers instead of going quietly offline.
- Outbound-only. Per-device revocable credential, hashed server-side, stored locally with
restrictive permissions. Runtime metadata from a custom server requires an explicit
--trust-runtimedecision. - No local history. Tool arguments and outputs are never written to a log on your computer.
Both the client and the runtime collect opt-out usage metrics: tool names, durations, outcomes, coarse error classes, session counts, and device health samples. They never include file paths, file contents, command strings, tool arguments, or tool output — the event schema is a whitelist, so those fields have nowhere to travel.
There is no telemetry endpoint and no third-party processor. The runtime emits MCP notifications to the agent, and the agent forwards them over the authenticated WebSocket it already holds to your ReMCP account. No install ping, no postinstall script, no remote feature flags, no A/B assignment.
remcp telemetry off # one switch for the client and the runtime
remcp telemetry statusnpm install
npm run check
npm testBoth workspaces are plain ESM with no build step. The contract commands (--help, --version,
--print-tools, --describe) work with no dependencies installed, so CI can diff the advertised
tool surface against the published tarball.
MIT.