Shell Use vs Remote Agents
A side-by-side look at the Shell Use and Remote Agents MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shell Use for command line work; choose Remote Agents for command line as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Shell Use when
- You need dedicated capabilities in the Command Line domain.
- You have the keys it needs:
SHELL_USE_SESSIONS, SHELL_USE_SOCKET.
Choose Remote Agents when
- You need dedicated capabilities in the Command Line domain.
- You prefer a local stdio subprocess transport.
- You want tools like
exec, read_file, get_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Command Line | Command Line |
| Quality signal | 25/100 · Emerging | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SHELL_USE_SESSIONSSHELL_USE_SOCKET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Shell Use | View Remote Agents |
Tools & capabilities
Shell Use tools
No tool names declared yet. Check the project README from the listing page.
Remote Agents tools 15
execRun a shell command (locally or on a remote agent via `agent_id`)read_fileFile operations (write requires Edit/Bypass)get_infoInspect / change an agent's mode at runtimegit_statusGit operationsschedule_addCron-style tasks on a hosttask_dispatchAutonomous AI tasks run with the host's own credentialssession_listBrowse the host's AI-chat history (claude / opencode / codex / cline / roo / kilo / zed / cursor / gemini / qwen / goose / continue); `session_get` fetches a transcript or a window around one messagesession_searchFull-text search over the host's AI-chat history — a local Tantivy (BM25) index of every provider transcript, returning ranked cited snippets with `session_id` + message position (follow up with `session_get { around_seq }` for the context)list_agentsList agents connected to the relay roomfleet_execRun an operation across the fleet — `target = all \fleet_session_searchSearch the AI-chat history across the whole fleet: every matched host queries its local index, hits merge by score with host labelsfile_searchFind files on a host, and move a file host→host (UDP, SHA-256 verified)- +3 more on 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.
Shell Use
No confirmed install command for Shell Use yet — follow the setup steps linked from its listing page rather than a guessed package name.
Remote Agents
{
"mcpServers": {
"remote-agents": {
"command": "npx",
"args": [
"-y",
"remote-agents"
]
}
}
}