Remote Agents vs Ssh Client MCP Server

A side-by-side look at the Remote Agents and Ssh Client MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Remote Agents logoRemote AgentsCommand Line · Local subprocess (stdio)Control fleets of remote machines via AI agents: exec, files, git, fleet ops, map/reduce.56GoodAuth: not declaredSsh Client MCP Server logoSsh Client MCP ServerCommand Line · Local subprocess (stdio)MCP server for executing shell commands on remote hosts via SSH.53GoodAuth: not declared

Verdict: choose Remote Agents for command line work as a local process; choose Ssh Client MCP Server 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?

Remote Agents logoChoose 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.
Explore Remote Agents

Ssh Client MCP Server logoChoose Ssh Client MCP Server when

  • You need dedicated capabilities in the Command Line domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like exec, soma_health, soma_capabilities.
Explore Ssh Client MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRemote Agents logoRemote AgentsSsh Client MCP Server logoSsh Client MCP Server
CategoryCommand LineCommand Line
Quality signal56/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars13
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools154

Tools & capabilities

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 runtime
  • git_statusGit operations
  • schedule_addCron-style tasks on a host
  • task_dispatchAutonomous AI tasks run with the host's own credentials
  • session_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 message
  • session_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 room
  • fleet_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 labels
  • file_searchFind files on a host, and move a file host→host (UDP, SHA-256 verified)
  • +3 more on the listing page

Ssh Client MCP Server tools 4

  • execExecute a shell command on the remote SSH server and return stdout.
  • soma_healthServer uptime, status, active session count.
  • soma_capabilitiesEnumerate registered tools, resources, and prompts.
  • soma_connectionsGateway connection status (unused here).

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.

Remote Agents

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "remote-agents": {
      "command": "npx",
      "args": [
        "-y",
        "remote-agents"
      ]
    }
  }
}

Ssh Client MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ssh-client-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "ssh-client-mcp-server"
      ]
    }
  }
}

Frequently asked questions

Remote Agents is categorized under Command Line and uses a local stdio subprocess. Ssh Client MCP Server belongs to Command Line and uses a local stdio subprocess. Pick Remote Agents for command line work and Ssh Client MCP Server for command line.

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.

Remote Agents has no declared pricing — check the project's own site. Ssh Client MCP Server has no declared pricing — check the project's own site. 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 remote-agents and ssh-client-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Remote Agents has a quality signal of 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Ssh Client MCP Server has 53/100 (Good) with 2 views, 0 installs and 3 GitHub stars.