Grok Build vs Ssh MCP

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

Grok Build logoGrok BuildCoding Agents · Local subprocess (stdio)Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research.53GoodAuth: not declaredSsh MCP logoSsh MCPCoding Agents · Local subprocess (stdio)MCP server exposing SSH control for Linux and Windows servers via Model Context Protocol. Securely execute remote shell commands with password or SSH key authentication.69GreatAuth: other

Verdict: choose Grok Build for coding agents work as a local process; choose Ssh MCP 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?

Grok Build logoChoose Grok Build when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like grok, review, websearch.
Explore Grok Build

Ssh MCP logoChoose Ssh MCP when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: SSH_MCP_PASSWORD, SSH_AUTH_SOCK.
  • You want tools like list-connections, list-sessions, open-session.
Explore Ssh MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGrok Build logoGrok BuildSsh MCP logoSsh MCP
CategoryCoding AgentsCoding Agents
Quality signal53/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedSSH_MCP_PASSWORDSSH_AUTH_SOCK
Verified ownerCommunity listingCommunity listing
GitHub stars0821
Directory activity 0 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools815

Tools & capabilities

Grok Build tools 8

  • grokRun a headless Grok agent. Prompt, session resume/continue/fork, model, effort, tool allow/deny
  • reviewReview a git diff: working tree, a merge-base diff against a ref, or a single commit
  • websearchResearch a question on the web, and report which searches and sources it actually used
  • statusPoll a background run, or list recent ones
  • stopTerminate a background run's process tree
  • sessionsList, search, and look up the Grok sessions on this machine
  • checkServer version, resolved binary, `grok version`, auth, permission ceiling, run defaults
  • helpgrok --help` passthrough

Ssh MCP tools 15

  • list-connectionsDiscover available hosts and connection status
  • list-sessionsList active sessions per host
  • open-sessionCreate a named interactive (stateful) or background session
  • close-sessionClose a session. A background session's command is signalled (INT/TERM/KILL) before its channel is dropped
  • read-session-outputRead output from background sessions (e.g., `tail -f`)
  • read-commandExecute allowlisted read-only commands (`ls`, `cat`, `grep`, ...)
  • run-commandExecute arbitrary commands (destructive/privileged need approval, unless `approvalPolicy = "auto"`)
  • privileged-commandExecute with sudo (needs approval, unless `approvalPolicy = "auto"`)
  • sftp-uploadUpload a file via SFTP (replaces the destination unconditionally)
  • sftp-downloadDownload a file via SFTP
  • sftp-listList a remote directory, bounded in entries and bytes
  • sftp-upload-fileStream a local file to the remote host, never through model context
  • +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.

Grok Build

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

Ssh MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tufantunc-ssh-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ssh-mcp"
      ],
      "env": {
        "SSH_MCP_PASSWORD": "YOUR_SSH_MCP_PASSWORD_HERE",
        "SSH_AUTH_SOCK": "YOUR_SSH_AUTH_SOCK_HERE"
      }
    }
  }
}

Frequently asked questions

Grok Build is categorized under Coding Agents and uses a local stdio subprocess. Ssh MCP belongs to Coding Agents and uses a local stdio subprocess. Pick Grok Build for coding agents work and Ssh MCP 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.

Grok Build has no declared pricing — check the project's own site. Ssh MCP is listed as free. Auth: other. 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 grok-build and tufantunc-ssh-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Grok Build has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Ssh MCP has 69/100 (Great) with 8 views, 0 installs and 821 GitHub stars.