What is the key difference between MCP Remote Ssh and Terminal History MCP?

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

How do I install MCP Remote Ssh or Terminal History MCP 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 Terminal History MCP free or paid?

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

Which MCP server has more tools and community activity?

MCP Remote Ssh lists 24 tools with 4 views and 10 GitHub stars. Terminal History MCP lists 5 tools with 1 views and 4 GitHub stars.

Can I use both MCP Remote Ssh and Terminal History MCP 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 Terminal History MCP

In-depth architectural comparison of the MCP Remote Ssh and Terminal History MCP 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: 60/100 (Good) | Auth: other

Terminal History MCP

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 Terminal History MCP 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 Terminal History MCP 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: reindex, search_history, recent_in_dir.

Explore Terminal History MCP Details

Feature & Specification Comparison

Specification	MCP Remote Ssh faizbawa Command Line	Terminal History MCP HasanJahidul 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	Full-text search over your shell history (zsh / bash / fish) via SQLite FTS5. Local-only. 11-pattern secret redaction runs BEFORE insert. Captures cwd / exit code / duration via opt-in shell hook. Tools: searchhistory, recentindir, failedcommands, commandchains, reindex.
Category & Scope

Tools & Capabilities Breakdown

MCP Remote Ssh Tools (24)

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

Execute a command with sudo on the remote host. If the user already has passwordless sudo, leave sudo_password empty. If secrets have been loaded via ssh_load_env_file, they are automatically injected as environment variables for this command.

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"
      ]
    }
  }
}

Terminal History MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hasanjahidul-terminal-history-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcpize"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to MCP Remote Ssh More alternatives to Terminal History MCP Command Line category hub