Remote Desktop Commander

Servidor MCP de Desktop Commander

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

Inicio de sesión OAuth (Inicias sesión con el proveedor la primera vez que te conectas)Streamable HTTP

Conectar con Remote Desktop Commander

Remote Desktop Commander requiere iniciar sesión. Conéctate con su propia URL:

https://mcp.desktopcommander.app/mcp

La primera vez, tu cliente abre el inicio de sesión de Desktop Commander. El token queda entre tu cliente y Desktop Commander.

Compartir este servidor

Abre esta página, con la URL y los pasos de configuración.

mcp.tc/i/remote-desktop-commander

Descripción

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.

Qué puedes hacer

  • 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

Herramientas

Remote Desktop Commander solo muestra sus herramientas después de iniciar sesión, así que no podemos listarlas aquí. Tu cliente las muestra cuando te conectes.

Prompts de ejemplo

  • 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.

Configuración

Todos los clientes se conectan a mcp.desktopcommander.app, y la primera vez Desktop Commander te pide que inicies sesión. Elige el tuyo; la página recuerda tu elección.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http remote-desktop-commander https://mcp.desktopcommander.app/mcp
  1. 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:
https://mcp.desktopcommander.app/mcp
  1. 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:
  1. Check that the URL reads https://mcp.desktopcommander.app/mcp and click Add.
  2. 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

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

mcp.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

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "remote-desktop-commander": {
      "serverUrl": "https://mcp.desktopcommander.app/mcp"
    }
  }
}
  1. 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

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
[mcp_servers.remote-desktop-commander]
url = "https://mcp.desktopcommander.app/mcp"

Gemini CLI

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.

{
  "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.

Preguntas frecuentes

Can I paste mcp.tc/i/remote-desktop-commander into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.desktopcommander.app/mcp, so your client talks to Remote Desktop Commander directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Remote Desktop Commander need an API key or a sign-in?

Yes, you need a Desktop Commander account. The first time your client connects, it opens Desktop Commander’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Remote Desktop Commander a remote or a local server?

Remote. Desktop Commander hosts it at https://mcp.desktopcommander.app/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Remote Desktop Commander do?

You can read, write and edit files on your paired computer, list directories and search files and content y start and interact with terminal processes and REPL sessions.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc’s robot read Remote Desktop Commander’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Insertar

Muestra Remote Desktop Commander en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones

Insignia para README

Vista previa de la insignia, claraVista previa de la insignia, oscura
Markdown
[![Remote Desktop Commander on mcp.tc](https://mcp.tc/i/remote-desktop-commander/badge.svg)](https://mcp.tc/i/remote-desktop-commander)
HTML
<a href="https://mcp.tc/i/remote-desktop-commander"><img src="https://mcp.tc/i/remote-desktop-commander/badge.svg" alt="Remote Desktop Commander on mcp.tc" height="20"></a>

Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.

Tarjeta para web

HTML
<script src="https://mcp.tc/w/remote-desktop-commander.js" async></script>

La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/remote-desktop-commander" title="Remote Desktop Commander on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.

JSON

La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).

https://mcp.tc/i/remote-desktop-commander.json

Qué significa cada campo

mcp.tc no tiene relación con Desktop Commander. Esta página se creó a partir de los metadatos públicos de Remote Desktop Commander, comprobados por última vez el 4 oct 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha.