Desktop Commander MCP MCP server

Which servers in the official MCP registry are Desktop Commander MCP's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to Desktop Commander MCP

Whose server it is

Registry nameapp.desktopcommander/remote-desktop-commanderverified in the MCP registry

The registry name sits under desktopcommander.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-08

Staterequires sign-inchecked 2026-10-08

On 2026-10-08 the server answered and asked for a sign-in with a Desktop Commander MCP account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

The first time it connects, the client opens a Desktop Commander MCP sign-in.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.