MCP Shell Server vs DesktopCommanderMCP
A side-by-side look at the MCP Shell Server and DesktopCommanderMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Shell Server for coding agents work as a local process; choose DesktopCommanderMCP for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Shell Server when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ALLOW_COMMANDS, ALLOWED_COMMANDS, ALLOW_PATTERNS. - You want tools like
shell_execute.
Choose DesktopCommanderMCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 64/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | ALLOW_COMMANDSALLOWED_COMMANDSALLOW_PATTERNS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 201 | 10,105 |
| Directory activity | 4 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View MCP Shell Server | View DesktopCommanderMCP |
Tools & capabilities
MCP Shell Server tools 1
shell_executeExecute a shell command Allowed commands: Allowed patterns: Default timeout: 30s; maximum timeout: 300s; output cap: 1048576 bytes
DesktopCommanderMCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Shell Server
{
"mcpServers": {
"tumf-mcp-shell-server": {
"command": "uvx",
"args": [
"mcp-shell-server"
],
"env": {
"ALLOW_COMMANDS": "YOUR_ALLOW_COMMANDS_HERE",
"ALLOWED_COMMANDS": "YOUR_ALLOWED_COMMANDS_HERE",
"ALLOW_PATTERNS": "YOUR_ALLOW_PATTERNS_HERE"
}
}
}
}
DesktopCommanderMCP
{
"mcpServers": {
"wonderwhy-er-desktopcommandermcp": {
"command": "npx",
"args": [
"-y",
"@wonderwhy-er/desktop-commander@latest"
]
}
}
}
Frequently asked questions
MCP Shell Server is categorized under Coding Agents and uses a local stdio subprocess. DesktopCommanderMCP belongs to Coding Agents and uses a local stdio subprocess. Pick MCP Shell Server for coding agents work and DesktopCommanderMCP for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Shell Server is listed as free. Auth: no auth required. DesktopCommanderMCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tumf-mcp-shell-server and wonderwhy-er-desktopcommandermcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Shell Server has a quality signal of 64/100 (Good) with 4 views, 0 installs and 201 GitHub stars. DesktopCommanderMCP has 56/100 (Good) with 3 views, 0 installs and 10,105 GitHub stars.