# Remote Desktop Commander MCP server

> Give claude.ai, ChatGPT, Cursor and other AI apps file and terminal access to your own computer through a hosted relay.

- Listing: https://mcp.tc/i/remote-desktop-commander
- Connect: use the server's own URL `https://mcp.desktopcommander.app/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Desktop Commander
- Homepage: <https://mcp.desktopcommander.app>
- Repository: <https://github.com/desktop-commander/remote-desktop-commander>

## About

Remote Desktop Commander is a hosted MCP server that relays tool calls from AI apps to a computer you own. Your assistant can read, search and edit files, run terminal commands and manage processes on that machine, and you can pair several computers and address them by name.

It runs as a hosted Streamable HTTP endpoint with OAuth 2.0 sign-in. Each target computer must run a device agent started with npx (Node.js 18 or newer), which pairs through the OAuth device flow. A machine is reachable only while its agent is running. Tools run with your user account permissions. The service is in beta and the hosted implementation is proprietary.

## What it can do

- Read, write and edit files on your paired computer
- List directories and search files and content
- Start and interact with terminal processes and REPL sessions
- List and terminate system processes
- Pair multiple computers and address them by name
- Edit PDF files on disk
- Review configuration and recent tool activity

## Example prompts

- "List the contents of my home directory and tell me what's there."
- "Create a folder called ai-test in Documents and write a Python script in it that prints the date."
- "Start a Python REPL on my machine and tell me which pandas version is installed."
- "Search my home directory for files modified in the last 24 hours and group them by folder."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code, type `/mcp`, pick **remote-desktop-commander** and choose **Authenticate**. A browser window opens for the Desktop Commander sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Remote Desktop Commander** and paste this URL:

```url
https://mcp.desktopcommander.app/mcp
```

3. Click **Add**, then **Connect**, and sign in when Desktop Commander asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Remote%20Desktop%20Commander&connectorUrl=https%3A%2F%2Fmcp.desktopcommander.app%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.desktopcommander.app/mcp` and click **Add**.

3. Click **Connect** and sign in when Desktop Commander asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://mcp.desktopcommander.app/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Desktop Commander to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=remote-desktop-commander&config=eyJ1cmwiOiJodHRwczovL21jcC5kZXNrdG9wY29tbWFuZGVyLmFwcC9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=remote-desktop-commander&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.desktopcommander.app%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"remote-desktop-commander","type":"http","url":"https://mcp.desktopcommander.app/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

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

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add remote-desktop-commander --url https://mcp.desktopcommander.app/mcp
codex mcp login remote-desktop-commander
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.remote-desktop-commander]
url = "https://mcp.desktopcommander.app/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http remote-desktop-commander https://mcp.desktopcommander.app/mcp
```

Then, inside Gemini CLI, run `/mcp auth remote-desktop-commander` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.desktopcommander.app/mcp`.

## Details

- Server version: 1.0.3
- Last checked: 2026-10-04 (reachable, asks for credentials)
- Listed: 2026-10-04
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/remote-desktop-commander (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
