Exa MCP Server vs Remote Ssh MCP

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

Exa MCP Server logoExa MCP ServerSearch & Data Extraction · Local subprocess (stdio)A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.73GreatAuth: no auth requiredRemote Ssh MCP logoRemote Ssh MCPCommand Line · Local subprocess (stdio)Persistent stateful remote SSH sessions for AI agents via MCP + OpenSSH.60GoodAuth: not declared

Verdict: choose Exa MCP Server for search & data extraction work as a local process; choose Remote Ssh MCP 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?

Exa MCP Server logoChoose Exa MCP Server when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like web_search_exa, web_fetch_exa.
Explore Exa MCP Server

Remote Ssh MCP logoChoose Remote Ssh MCP when

  • You need dedicated capabilities in the Command Line domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like ssh_hosts, ssh_open, ssh_run.
Explore Remote Ssh MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecExa MCP Server logoExa MCP ServerRemote Ssh MCP logoRemote Ssh MCP
CategorySearch & Data ExtractionCommand Line
Quality signal73/100 · Great60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,1651
Directory activity 11 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools27

Tools & capabilities

Exa MCP Server tools 2

  • web_search_exaSearch the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
  • web_fetch_exaRead a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).

Remote Ssh MCP tools 7

  • ssh_hostsList allowed OpenSSH Host aliases discovered from the local ssh_config (and explicit allowlist). Returns only safe connection metadata: alias, hostname, user, port, proxy_jump. Never returns private keys, IdentityFile paths, agent sockets, or ProxyCommand. Pass reload=true after editing ~/.ssh/config to re-parse without restarting the MCP server. Use an alias from this list with ssh_open.
  • ssh_openOpen a new persistent remote bash shell for an allowed ssh_config Host alias from ssh_hosts. Each call creates a clean session with a new id. Credentials come only from local OpenSSH configuration/agent; passwords and private keys are never accepted as arguments and must not be read from disk by the model.
  • ssh_runStart a non-interactive command in the same persistent shell identified by id. cwd and environment changes persist. The call waits at most wait_sec (default 10 seconds); if the command is still active it returns status=running without stopping it. Commands have no automatic execution timeout by default. Only an explicitly provided timeout_sec sends Ctrl-C at that deadline. Never retry a running command: poll with ssh_peek(wait_sec=...) so the MCP call blocks until idle or the wait expires; do not spam peeks with wait_sec=0. Call ssh_interrupt to stop it, or open another session for concurrent work. Only one foreground command may run per id. Do not use vim, top, password prompts, or other interactive TUI/input flows.
  • ssh_peekObserve the current foreground command and its latest output without starting another command. When status=running, optional wait_sec (default 0) long-polls this MCP call until the command finishes or the wait expires—prefer a positive wait_sec over busy-looping. wait_sec never stops the remote command. Returns the newest lines in chronological order, limited independently for stdout and stderr; lines defaults to 50 and is capped to protect model context. Use after ssh_run returns status=running. When idle, returns immediately with cwd, last exit code, and the latest lines from the completed command.
  • ssh_interruptSend Ctrl-C to the current foreground process group and wait for the shell protocol to recover. The session is kept only when recovery is confirmed. Returns nothing_to_interrupt when idle.
  • ssh_listList all live sessions with host, cwd, state, last exit code, idle time, idle-reap countdown, and connection capacity. Use this to recover valid ids; never invent one.
  • ssh_closeClose the remote shell and SSH connection, clean its private temporary directory, and invalidate the id. Close a dirty session and call ssh_open for a clean environment.

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.

Exa MCP Server

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

Remote Ssh MCP

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

Frequently asked questions

Exa MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. Remote Ssh MCP belongs to Command Line and uses a local stdio subprocess. Pick Exa MCP Server for search & data extraction work and Remote Ssh MCP 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.

Exa MCP Server is listed as free. Auth: no auth required. Remote Ssh MCP 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 exa-labs-exa-mcp-server and remote-ssh-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Exa MCP Server has a quality signal of 73/100 (Great) with 11 views, 0 installs and 5,165 GitHub stars. Remote Ssh MCP has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.