Remote Desktop Commander

Name: Remote Desktop Commander
Author: desktop-commander

by desktop-commanderversion 1.1.21i★ 211iRuns in the cloud

Registry nameapp.desktopcommander/remote-desktop-commander

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi4 of 5 passedChecked from public information; code not scanned yet
UsageiEarly★ 211

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

Runs in the cloudNothing to install; it connects over the internet

Claude DesktopClaude CodeCursorVS Code

Open Claude Desktop → Settings → Connectors → Add custom connector, and paste this address

https://mcp.desktopcommander.app/mcp

Run this in your terminal

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

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Paste into .vscode/mcp.json in your project

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain desktopcommander.app (the registry checks domain ownership)
✓ Pass
Still maintained
Code last changed today
! Caution
Has a licence
GitHub could not identify the licence type; open the file to check
✓ Pass
Endpoint responds
Responded in 346 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Needs the server’s tool list first; this check starts in the next step

Compared with others in Otheri

More stars than 0% of the other 1 servers in this category
Published to the registry more recently than 100% of the other 1 servers in this category
Basic checks equal to or better than 100% of the other 1 servers in this category

Compared only with servers in this prototype, not the whole registry.

Common questions

Is Remote Desktop Commander safe?

It passed 4 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed today, and the latest version (1.1.21) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 13 months ago

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

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.

claude.ai / Claude Desktop — Settings → Connectors → Add custom connector, then enter:

https://mcp.desktopcommander.app/mcp

Claude Code:

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

(If you work inside a checkout of this repo, Claude Code also picks up the included .mcp.json automatically.)

ChatGPT — Settings → Apps & Connectors → Advanced settings → enable Developer mode (requires a plan that includes it), then Create connector and enter:

https://mcp.desktopcommander.app/mcp

Cursor — one click: Add to Cursor. Or add to ~/.cursor/mcp.json manually:

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

VS Code — install the agent plugin (bundles this server):

copilot plugin install desktop-commander/remote-desktop-commander

Or add the server directly to .vscode/mcp.json in your workspace (or your user-level mcp.json):

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

Gemini CLI:

gemini extensions install https://github.com/desktop-commander/remote-desktop-commander

3. Try it

These work against any machine running the agent, no setup needed:

"List the contents of my home directory and tell me what's there."

"Create a folder called ai-test in my Documents folder. Inside it, write a short Python script that prints the date, and run it."

"Start a Python REPL on my machine, import pandas, and tell me which version is installed. Keep the session alive."

"Search my home directory for files modified in the last 24 hours and group them by folder."

Full walkthrough with troubleshooting: docs/SETUP.md

Requirements

Node.js 18 or newer (for npx) on each computer you want to control
One terminal running the device agent per machine
Works on macOS, Windows, and Linux

Available tools

Category	Tools
Read & explore	Read File, Read Multiple Files, List Directory, Get File Info
Search	Start Search, Get More Search Results, Stop Search, List Active Searches
Write & edit	Write File, Edit File Block, Move or Rename File, Create Directory, Write or Modify PDF
Terminal & processes	Start Process, Send Input to Process, Read Process Output, List Active Sessions, List System Processes, Terminate Session, Kill System Process
Devices & account	List Paired Devices, Current User Info, Ping Device, Shutdown Device Agent
Configuration & help	Get Configuration, Set Configuration Value, Get Prompt Library, Get Recent Tool Activity, Get Usage Statistics, Submit Feedback

How it works

sequenceDiagram

participant AI as AI app (web, mobile, desktop) participant S as mcp.desktopcommander.app participant D as Your computer (device agent) AI->>S: MCP tool call (OAuth 2.0 bearer) S->>D: relayed to your paired device D->>D: executes locally D->>S: result S->>AI: MCP response

Authentication is standard OAuth 2.0 with PKCE; devices pair via the OAuth device authorization flow (the short-code approval you see at setup).
The server only accesses data explicitly requested through tool calls; transmission is encrypted in transit (HTTPS/TLS).
A machine is reachable only while its device agent is running — stop it with Ctrl+C and access ends. Devices can also be reviewed and revoked at any time from the dashboard.
Tools execute with your user account's permissions on the paired machine, so treat your connected AI accounts like credentials and protect them with MFA. Read the full trust model in SECURITY.md.

Support & legal

Setup guide: docs/SETUP.md
Bugs & feature requests: GitHub Issues · Contributing: CONTRIBUTING.md
Community: Discord
Security reports: see SECURITY.md
Privacy policy: Remote Desktop Commander privacy policy · Terms of service: legal.desktopcommander.app
License: LICENSE — this repository holds docs and manifests only; the hosted service is proprietary

DesktopCommanderMCP — the open-source local MCP server (npm: @wonderwhy-er/desktop-commander), which also ships the remote device agent used for pairing
desktopcommander.app — product site

Remote Desktop Commander

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

README from the maker

Remote Desktop Commander

What you can do

Quick start

1. Start the device agent

2. Connect your AI client

3. Try it

Requirements

Available tools

How it works

Support & legal

Related