What is the key difference between MCP Remote Ssh and Execkit?

MCP Remote Ssh belongs to the Command Line category with local stdio execution, while Execkit belongs to the Command Line category with local stdio execution.

How do I install MCP Remote Ssh or Execkit in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Remote Ssh and Execkit free or paid?

MCP Remote Ssh operates under a Free / Open Source model (other). Execkit operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP Remote Ssh lists 20 tools with 4 views and 10 GitHub stars. Execkit lists 6 tools with 3 views and 7 GitHub stars.

Can I use both MCP Remote Ssh and Execkit together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Remote Ssh vs Execkit

In-depth architectural comparison of the MCP Remote Ssh and Execkit MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Remote Ssh

Command Line · Local stdio

Quality: 63/100 (Good) | Auth: other

Execkit

Command Line · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose MCP Remote Ssh if you need specialized Command Line tools running via a local process. Choose Execkit if your workspace requires Command Line integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Remote Ssh when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: ssh_connect, ssh_list_sessions, ssh_close_session.

Explore MCP Remote Ssh Details

Choose Execkit when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: session_checkpoint, session_checkpoints, session_create.

Explore Execkit Details

Feature & Specification Comparison

Specification	MCP Remote Ssh faizbawa Command Line	Execkit blinkingbit-oss Command Line
Summary	Full SSH access for AI agents with secret-safe environment injection and automatic output redaction. Persistent sessions, structured execution, SFTP, port forwarding — secrets are fed via stdin (invisible to ps) and scrubbed from all tool responses before reaching the LLM. uvx mcp-remote-ssh	Stateful, structured, auditable shell sessions for AI agents over local, SSH, and Docker. Secret redaction, output budgeting, SSH host-key verification, and a loopback read-only browser viewer that streams the live transcript.
Category & Scope

Tools & Capabilities Breakdown

MCP Remote Ssh Tools (20)

ssh_connect

Connect to a remote host via SSH. Returns a session_id for use with all other tools. Supports password and key-based authentication.

ssh_list_sessions

List all active SSH sessions with their connection status and details. Returns: List of session info dicts.

ssh_close_session

Close an SSH session and release all its resources (shell, SFTP, port forwards). WARNING: this kills any running processes in the session.

ssh_execute

Execute a command on the remote host and return structured output. Each call runs in an independent exec channel -- no state is shared between calls (use ssh_shell_* tools for persistent state). If secrets have been loaded via ssh_load_env_file, they are automatically injected as environment variables for this command.

ssh_sudo_execute

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Remote Ssh Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "faizbawa-mcp-remote-ssh": {
      "command": "uvx",
      "args": [
        "mcp-remote-ssh"
      ]
    }
  }
}

Execkit Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "blinkingbit-oss-execkit": {
      "command": "uvx",
      "args": [
        "execkit-mcp"
      ]
    }
  }
}

Frequently Asked Questions

MCP Remote Ssh is categorized under Command Line and uses a local stdio subprocess. In contrast, Execkit belongs to Command Line using local stdio subprocess. Select MCP Remote Ssh when you need capabilities focused on command line and Execkit when you require tools for command line.

More alternatives to MCP Remote Ssh More alternatives to Execkit Command Line category hub Canonical compare URL