Dev Tools & GitMCP RegistryremoteA · 81

Remote Desktop Commander MCP server

Name: Remote Desktop Commander
Author: desktopcommander.app

app.desktopcommander · Updated today

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

At a glance

Remote Desktop Commander is an MCP server in the Dev Tools & Git category. It is hosted remotely and connects over HTTP, and declares no required credentials. It scores A (81/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 201

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Remote Desktop Commander in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Remote Desktop Commander in Claude CodeAnthropic's agentic CLI

Add the server

bash

claude mcp add --transport http remote-desktop-commander https://mcp.desktopcommander.app/mcp

2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.

How to install Remote Desktop Commander in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "remote-desktop-commander": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.desktopcommander.app/mcp"
      ]
    }
  }
}

Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install Remote Desktop Commander in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "remote-desktop-commander": {
      "url": "https://mcp.desktopcommander.app/mcp"
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install Remote Desktop Commander in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.remote-desktop-commander]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.desktopcommander.app/mcp"]

Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install Remote Desktop Commander in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "remote-desktop-commander": {
      "serverUrl": "https://mcp.desktopcommander.app/mcp"
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install Remote Desktop Commander in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "remote-desktop-commander": {
      "type": "streamableHttp",
      "url": "https://mcp.desktopcommander.app/mcp"
    }
  }
}

How to install Remote Desktop Commander in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "remote-desktop-commander": {
      "type": "http",
      "url": "https://mcp.desktopcommander.app/mcp"
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does Remote Desktop Commander expose?

This server requires credentials before it will list its tools, so we cannot enumerate them here. Connect it in your client to see what it offers.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Third-party hosted service — Your requests and any data in them are sent to mcp.desktopcommander.app.
No local execution — Nothing is installed or run on your machine.

Last commit today — Actively maintained.
201 GitHub stars — Community adoption signal.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 81

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 0 days ago.
Adoption20%70%
201 stars.
Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%75%
Remote endpoint; authentication requirements not declared.

Documentation

Full README

Remote Desktop Commander

Build, explore, automate on your computer — from anywhere.

Reach your computer's filesystem and terminal from any AI app that supports remote MCP connectors. Remote Desktop Commander is a hosted MCP server that relays a secure connection to your real machine, giving your AI assistant the same full file and shell access as the local server — without you needing to be at the keyboard.

Server endpoint: https://mcp.desktopcommander.app/mcp (Streamable HTTP, OAuth 2.0)
Dashboard: mcp.desktopcommander.app
Status: currently in beta
Demo: watch the video

This repository hosts the public manifests, documentation and issue tracker for the hosted service. The service implementation is not open source. For the open-source local (stdio) server, see DesktopCommanderMCP.

What you can do

Build from scratch — create features and applications with simple commands
Manage development environments — set up servers, configure systems, handle processes
Explore existing codebases — navigate and understand complex repositories
Edit documents in place — work on Word, Excel, and PDF files where they live on disk
Manage context and documentation — keep track of project details and technical specifications
Control multiple machines — pair several computers and address them by name in one conversation

Quick start

1. Start the device agent

On the computer you want to control:

bash

npx @wonderwhy-er/desktop-commander@latest remote

Your browser opens to a verification page showing a pairing code (also printed in the terminal — a standard OAuth device-flow check). Sign in, confirm the codes match, and the terminal reports "Device ready". Keep the agent running: close the terminal, no access.

2. Connect your AI client

Each client walks you through OAuth sign-in on first connect.

Excerpt — the full document is on GitHub.

Alternatives to Remote Desktop Commander

Maintain Remote Desktop Commander? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![Remote Desktop Commander on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/app-desktopcommander-remote-desktop-commander)](https://mcp-skills-hub.vercel.app/mcps/app-desktopcommander-remote-desktop-commander)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.