Does Desktop Commander have an MCP server?
Desktop Commander maintains an official MCP server.
The hosted server is in beta and relays to a device agent you run on your own computer.
- Access
- Remote server
- Endpoint
- https://mcp.desktopcommander.app/mcp
- Package
- @wonderwhy-er/desktop-commander
- Repository
- wonderwhy-er/DesktopCommanderMCP
- Maintainer
- Eduard Ruzga
- License
- MIT
- Language
- TypeScript
- Stars
- 9.8k
- Last commit
- today
- Category
- File Systems
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
Project site: desktopcommander.app
A remote server run by Desktop Commander itself — nothing to install. Documented at desktopcommander.app.
Published on npm. The package page carries the exact launch arguments and required credentials.
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http desktopcommander https://mcp.desktopcommander.app/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.desktopcommander.app/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"desktopcommander": {
"url": "https://mcp.desktopcommander.app/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"desktopcommander": {
"type": "http",
"url": "https://mcp.desktopcommander.app/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.desktopcommander.app/mcp - Complete sign-in, then enable the connector in a new chat
Does Desktop Commander have an official MCP server?
Yes. Desktop Commander maintains an official MCP server, hosted at https://mcp.desktopcommander.app/mcp, distributed as @wonderwhy-er/desktop-commander on npm. The source lives at wonderwhy-er/DesktopCommanderMCP on GitHub.
How do I connect Desktop Commander to Claude?
Add https://mcp.desktopcommander.app/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http desktop-commander https://mcp.desktopcommander.app/mcp" in Claude Code.
Do I need to install anything to use the Desktop Commander MCP server?
No. It is a remote server hosted by Desktop Commander, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under app.desktopcommander (Remote Desktop Commander); the hosted endpoint mcp.desktopcommander.app/mcp answers MCP initialize (401, OAuth required). desktopcommander.app documents both the remote server and the open-source local server wonderwhy-er/DesktopCommanderMCP, run with `npx -y @wonderwhy-er/desktop-commander@latest`. GitHub metadata is refreshed every six hours.
Published to the MCP Registry under app.desktopcommander (Remote Desktop Commander); the hosted endpoint mcp.desktopcommander.app/mcp answers MCP initialize (401, OAuth required). desktopcommander.app documents both the remote server and the open-source local server wonderwhy-er/DesktopCommanderMCP, run with `npx -y @wonderwhy-er/desktop-commander@latest`.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.