Skip to main content
Glama
ssh-mcp
by slepp

ssh-mcp

Give your AI coding agent access to remote machines through your local OpenSSH client. ssh-mcp lets agents run commands, transfer and edit files, keep interactive shells open, and create port forwards using your existing SSH config, keys, and credentials.

Run ssh-mcp on the machine where your MCP client runs. Your remote hosts only need SSH access and the usual command-line tools; you don't install an MCP server on them.

Why ssh-mcp?

  • Uses your local SSH — host aliases, ~/.ssh/config, ProxyJump, agent forwarding, and existing credentials all work naturally. No SSH libraries or key management.

  • Native-feeling remote editing — ssh_view/ssh_create/ssh_edit/ssh_grep/ssh_glob mirror the read/edit/search tools agents already use locally, so remote files can be read, searched, and edited exactly like local ones instead of through ad hoc cat/sed/grep commands.

  • Persistent sessions — agents can keep a shell open across multiple tool calls, just like a human would. A stable session_name lets an agent find the same session after a context reset, while the MCP server keeps running.

  • Observable — every session records a transcript and optionally launches a detached tmux viewer so you can watch what the agent is doing in real time.

  • Permission-gatable — port forwarding is a separate tool from command execution, so MCP clients can allow SSH access without allowing port forwards.

  • Pure Python — no third-party runtime dependencies. Uses Python 3.10+ and your system's OpenSSH tools.

Related MCP server: mcp-remote-ssh

Requirements

  • Python 3.10+ in a POSIX environment, such as macOS or Linux (interactive sessions and tty commands need a local PTY)

  • ssh and scp on PATH (or set SSH_MCP_SSH_BIN / SSH_MCP_SCP_BIN)

  • rsync locally and on the remote host — only needed for ssh_sync; set SSH_MCP_RSYNC_BIN to override the local executable

  • grep and find on the remote host — needed for ssh_grep / ssh_glob (present on effectively all POSIX systems)

  • tmux locally — optional, for live session observation

Check your SSH connection

First, connect from the machine that will run ssh-mcp. Replace my-server with an SSH host alias or user@hostname:

ssh my-server 'printf "connected\n"'

Verify the host fingerprint if SSH asks, and make sure your key or SSH agent is ready. Start with a host and account whose access you are comfortable giving the agent. ssh-mcp uses that account's permissions for remote commands and file changes.

Installation

With uv installed, your MCP client can launch ssh-mcp with:

uvx --from slepp-ssh-mcp ssh-mcp

This runs the ssh-mcp command from the slepp-ssh-mcp package. Running it directly waits for MCP requests on standard input; there is no interactive prompt.

To install the command persistently:

uv tool install slepp-ssh-mcp

With pip

Use a virtual environment:

python3 -m venv .venv
.venv/bin/python -m pip install slepp-ssh-mcp

Set your client's command to the absolute path to .venv/bin/ssh-mcp and use an empty args array. This keeps the server available even when the client starts outside your shell.

Connect your MCP client

The examples below use uvx. If it is not on your client's PATH, use its absolute path as command. Add entries to an existing configuration rather than replacing its other servers.

Claude Code

claude mcp add --transport stdio --scope user ssh-mcp -- uvx --from slepp-ssh-mcp ssh-mcp

Or commit a .mcp.json to share with your team:

{
  "mcpServers": {
    "ssh-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "slepp-ssh-mcp", "ssh-mcp"]
    }
  }
}

Codex CLI

codex mcp add ssh-mcp -- uvx --from slepp-ssh-mcp ssh-mcp

GitHub Copilot CLI

Add to ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "ssh-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "slepp-ssh-mcp", "ssh-mcp"],
      "tools": ["*"]
    }
  }
}

Use /mcp show ssh-mcp in Copilot CLI to check the server and its tools. If you authenticate through an SSH agent, add its SSH_AUTH_SOCK value to this server's env object; Copilot CLI inherits PATH automatically, while other environment variables need explicit configuration. See the Copilot CLI MCP guide for tool selection and environment configuration.

VS Code with GitHub Copilot

Create .vscode/mcp.json in your project, using VS Code's top-level servers key:

{
  "servers": {
    "ssh-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["--from", "slepp-ssh-mcp", "ssh-mcp"]
    }
  }
}

Review the configuration before trusting the workspace. Run MCP: List Servers from the Command Palette to start ssh-mcp, then select its tools in Copilot's agent chat. For a user-wide configuration, run MCP: Open User Configuration. See the VS Code MCP guide for configuration options.

Generic MCP client

Use a client that supports local stdio servers:

  • Command: uvx

  • Arguments: --from, slepp-ssh-mcp, ssh-mcp as three separate arguments

For a persistent installation, use the absolute path to the ssh-mcp executable with no arguments. The client starts and stops the server process.

Try your first command

Open your client's MCP tool list and confirm that ssh_exec is available. In Claude Code or a Codex session, use /mcp; in Copilot CLI, use /mcp show ssh-mcp; in VS Code, use MCP: List Servers. You can also check Codex's saved server configuration with codex mcp list.

Ask your agent:

Use ssh-mcp to run pwd and uname -a on my-server.

Replace my-server with the same target you checked earlier. The corresponding ssh_exec arguments are:

{
  "target": "my-server",
  "command": "pwd && uname -a",
  "timeout": 10
}

The result includes stdout, stderr, exit_code, and timed_out. These examples show tool arguments; your MCP client supplies the JSON-RPC request around them.

If setup fails

  • Server cannot start: check that the client can find uvx (or your installed ssh-mcp executable) and that it runs in an environment with Python 3.10+.

  • SSH fails or waits for authentication: repeat the terminal SSH check using the same target and account. Make sure the client process can reach your SSH config, keys, and SSH agent (SSH_AUTH_SOCK).

  • Tools are missing: check the configuration file's top-level key, then reconnect or restart the server and select its tools in your client.

How it works

ssh-mcp runs as a stdio process that your MCP client spawns. It receives JSON-RPC tool calls and translates them into local ssh/scp/rsync commands. Because it uses your local SSH binary, everything in your ~/.ssh/config works — jump hosts, custom ports, key selection, SSH_AUTH_SOCK, proxy commands.

There are five modes of operation:

One-off commands (ssh_exec)

Run a command, get stdout/stderr/exit code back. Works like ssh host 'command'.

{
  "target": "prod-web01",
  "command": "systemctl status nginx",
  "timeout": 10
}

Use cwd to set the working directory, env to export variables, and tty: true for commands that need a terminal (like sudo with a password prompt). Note that tty merges stdout and stderr.

Interactive sessions (ssh_ensure_session + ssh_write_session + ssh_read_session)

For multi-step work, open a persistent shell. The agent writes commands and reads output just like typing in a terminal.

Start or reuse a session:

{
  "target": "prod-web01",
  "session_name": "deploy-api"
}

Always use a descriptive session_name. It serves three purposes:

  1. The agent can find the same session across multiple tool calls

  2. The tmux observer window gets a human-readable name (e.g., ssh-mcp-prod-web01-deploy-api)

  3. Another conversation connected to the same running server can recover the session by name

Write a command:

{
  "session_id": "a1b2c3d4e5f6",
  "input": "cd /app && git pull\n",
  "wait_seconds": 5
}

Always include \n to press Enter. Use \u0003 for Ctrl-C, \u0004 for Ctrl-D. Set wait_seconds high enough for the command to produce output (default: 1 second).

Read more output:

{
  "session_id": "a1b2c3d4e5f6",
  "wait_seconds": 10
}

Check pending_output_chars in the response — if non-zero, call again to drain the buffer.

Session lifecycle:

  • Session names and IDs are scoped to the running MCP server and are lost when it restarts. Use ssh_stop_session and ssh_stop_forward to close sessions and forwards when finished.

  • ssh_ensure_session is idempotent — call it at the start of each step

  • Sessions auto-detect dead connections via SSH keepalive (~90 seconds)

  • Response includes uptime_seconds, idle_seconds, and exit_reason for health monitoring

  • Use auto_close: true for one-shot commands that should clean up when done

  • Exited sessions are pruned from memory after 1 hour (5 minutes for auto_close)

  • cwd, env, and shell only apply when creating a new session — they are ignored when reusing an existing one

File transfer (ssh_scp, ssh_sync)

Copy files between local and remote machines.

scp — simple file/directory copy:

{
  "target": "prod-web01",
  "direction": "upload",
  "sources": ["/local/path/app.tar.gz"],
  "destination": "/tmp/"
}

For upload, sources are local paths and destination is remote. For download, it's reversed. The target parameter specifies the host — don't include the host in sources or destination.

rsync — incremental sync with --delete and --exclude:

{
  "target": "prod-web01",
  "direction": "upload",
  "source": "./dist/",
  "destination": "/var/www/app/",
  "delete": true,
  "exclude": ["*.log", ".git"]
}

Remote file access (ssh_view, ssh_create, ssh_edit, ssh_grep, ssh_glob)

These mirror the read/edit/search tools agents use locally, but operate on files on the remote host — so remote editing feels the same as local editing instead of composing cat/sed/grep by hand over ssh_exec.

ssh_view — read a file or list a directory:

{
  "target": "prod-web01",
  "path": "/etc/nginx/nginx.conf"
}

Returns content, size_bytes, and total_lines. Content is truncated at 20KB by default — pass view_range: [start, end] (1-based, inclusive; end: -1 means "to end of file") to page through large files, or force_read_large_files: true to read the whole thing anyway. If path is a directory, returns non-hidden entries up to 2 levels deep instead.

ssh_create — write a brand-new remote file:

{
  "target": "prod-web01",
  "path": "/etc/systemd/system/myapp.service",
  "content": "[Unit]\nDescription=My app\n..."
}

Fails if path already exists or its parent directory doesn't, exactly like the local file-creation tool.

ssh_edit — exact string replacement in an existing file:

{
  "target": "prod-web01",
  "path": "/etc/nginx/nginx.conf",
  "edits": [
    {"old_str": "worker_processes 1;", "new_str": "worker_processes auto;"}
  ]
}

Each old_str must match exactly one location in the file (as it stands after any earlier edits in the same call) — ambiguous or missing matches fail without writing anything. Pass multiple {old_str, new_str} entries in edits to batch several changes into one round trip instead of one SSH connection per edit.

ssh_grep — search remote file contents:

{
  "target": "prod-web01",
  "pattern": "ERROR|WARN",
  "path": "/var/log/myapp",
  "glob": "*.log",
  "output_mode": "content"
}

output_mode is files_with_matches (default), content (matching lines, with line numbers and optional context/context_before/context_after), or count (per-file match counts; files with zero matches are omitted). Backed by remote grep, preferring PCRE-like -P when available and falling back to POSIX extended regex otherwise. Always skips .git/.hg/.svn.

ssh_glob — find remote files by name:

{
  "target": "prod-web01",
  "pattern": "src/**/*.ts",
  "path": "/srv/app"
}

Supports *, ?, [seq]/[!seq], {a,b} alternation, and ** (zero or more path segments). A path segment starting with . is only matched by a pattern segment that itself starts with ., matching classic Unix glob behavior.

All five tools raise a remote_file_error (see Tools reference) for problems like a missing path, a path that already exists, or an ambiguous/missing edit match — the on-the-wire outcome you'd expect from the equivalent local tool.

Port forwarding (ssh_forward)

Create local or remote port forwards. This is a separate tool from ssh_exec so MCP clients can grant SSH access without granting port forwarding.

Local forward — make a remote service reachable locally:

{
  "target": "prod-web01",
  "direction": "local",
  "local_port": 15432,
  "remote_host": "prod-db.internal",
  "remote_port": 5432
}

This binds localhost:15432 and tunnels it to prod-db.internal:5432 through prod-web01.

Remote forward — expose a local service on the remote host:

{
  "target": "prod-web01",
  "direction": "remote",
  "local_port": 3000,
  "remote_host": "localhost",
  "remote_port": 8080
}

Forwards bind to 127.0.0.1 by default. Set bind_address: "0.0.0.0" to expose on all interfaces (use with caution).

Use ssh_list_forwards to see active forwards and ssh_stop_forward to tear them down.

Watching sessions

Every interactive session records a transcript to ~/.local/state/ssh-mcp/<session_id>/transcript.log.

By default, sessions also launch a detached tmux window so you can watch in real time. The tmux session name includes the target and session name for easy identification:

# List ssh-mcp tmux sessions
tmux ls | grep ssh-mcp

# Attach to watch
tmux attach -t ssh-mcp-prod-web01-deploy-api

If you prefer not to use tmux, set observer_mode: "transcript" and tail the transcript file directly — the response includes an observer_command you can copy-paste.

The tmux observer is tied to the session lifecycle: stopping a session closes its tmux window. The MCP server also cleans up tmux on shutdown.

Environment variables

Variable

Default

Description

SSH_MCP_SSH_BIN

ssh

Path to the SSH client

SSH_MCP_SCP_BIN

scp

Path to the SCP client

SSH_MCP_RSYNC_BIN

rsync

Path to rsync

SSH_MCP_TMUX_BIN

tmux

Path to tmux

SSH_MCP_STATE_DIR

~/.local/state/ssh-mcp

Where transcripts are stored

Security

ssh-mcp is designed for single-developer use on your own machine. It runs SSH commands as your user with your credentials.

What's protected:

  • Port forwarding flags (-L, -R, -D, -W) and dangerous SSH options (ProxyCommand, LocalCommand, LocalForward, RemoteForward, DynamicForward) are blocked in extra_ssh_args. The only way to create forwards is through the explicit ssh_forward tool, which MCP clients can permission-gate.

  • Transcript files are created with mode 0600 and the state directory with 0700.

  • All command arguments use shlex.quote() to prevent shell injection. Subprocess calls use list arguments, never shell=True.

  • Environment variable names are validated against ^[A-Za-z_][A-Za-z0-9_]*$.

What's not protected:

  • An agent with ssh_exec access can run arbitrary commands on any host your SSH config can reach. The security boundary is SSH itself (keys, known_hosts).

  • Transcript files persist on disk after sessions end and may contain secrets (passwords typed at sudo prompts, API keys in output). Clean up SSH_MCP_STATE_DIR when you no longer need them.

  • The shell parameter lets agents choose any remote executable. This is by design — the tool is for remote execution.

Known limitations

  • POSIX-only remotes — cwd, env, and shell wrapping assumes a POSIX shell on the remote side. Windows SSH targets need commands written for their shell.

  • PTY output — interactive sessions use a PTY, so output includes terminal formatting (ANSI escape codes, command echo, line wrapping). This is intentional — it matches what a human would see.

  • No multiplexing — each ssh_exec call opens a new SSH connection. If your agent runs many rapid commands to the same host, consider using a session instead, or configure ControlMaster in your ~/.ssh/config.

  • Transcript growth — transcripts grow without bound for long-running sessions. The response includes transcript_size_bytes so you can monitor this. Restart the session if it gets too large.

  • Forward connections are standalone — each ssh_forward opens its own SSH connection. Forwards are not tied to sessions.

  • Remote file tools are text-oriented — ssh_view/ssh_create/ssh_edit decode remote content as UTF-8 with errors="replace"; binary files may come back with stray replacement characters. They're built for source/config files, like their local counterparts.

  • ssh_edit isn't fully atomic — it reads the file, applies edits locally, then writes the result back in a second SSH round trip. A concurrent external write between the two round trips could be overwritten, same class of risk as editing any file that's being modified elsewhere.

  • ssh_grep regex flavor depends on the remote — it prefers PCRE-like -P (closer to what agents expect) when the remote grep/ggrep supports it, otherwise falls back to POSIX extended regex (-E), which lacks things like \d/\w/\b. multiline matching isn't supported.

  • ssh_glob/ssh_grep list the whole subtree — matching happens after enumerating files under path via remote find; scope path to something reasonable on very large trees.

Tools reference

Tool

Description

ssh_exec

Run a one-off remote command

ssh_scp

Copy files via scp

ssh_sync

Incremental sync via rsync

ssh_view

Read a remote file (with paging) or list a remote directory

ssh_create

Create a new remote file

ssh_edit

Exact string replacement in an existing remote file

ssh_grep

Search remote file contents

ssh_glob

Find remote files by name pattern

ssh_start_session

Start a new interactive session

ssh_ensure_session

Reuse or start an interactive session (recommended)

ssh_read_session

Read output from a session

ssh_write_session

Write input to a session

ssh_stop_session

Stop a session

ssh_list_sessions

List tracked sessions

ssh_forward

Start a port forward

ssh_list_forwards

List tracked forwards

ssh_stop_forward

Stop a port forward

All session and forward tools accept standard SSH connection parameters: port, identity_file, known_hosts_file, strict_host_key_checking, and extra_ssh_args. So do ssh_view, ssh_create, ssh_edit, ssh_grep, and ssh_glob.

OpenAI function registration

The MCP tool schemas accept both booleans and strings for strict_host_key_checking: true maps to yes, false maps to no, and yes, no, ask, accept-new, and off select the OpenSSH mode. Omit the parameter to use your SSH configuration.

When adapting tools/list results to OpenAI function tools, copy each inputSchema to parameters and explicitly set strict: false. The schemas use supported anyOf unions, but preserve optional parameters and arbitrary env keys. OpenAI strict mode requires every property to be required and every object to set additionalProperties: false; enabling it directly would change those interfaces. See the OpenAI function-calling guide.

Development

python3 -m pip install build -e ".[test]"
python3 -m unittest discover -s tests -v
python3 -m compileall src
python3 -m build

License

MIT. See LICENSE.

Available Tools

17 tools
ssh_createA

Create a new remote file over SSH with the given content — the remote counterpart of the local file-creation tool. Fails if the path already exists (use ssh_edit to modify an existing file) or if the remote parent directory doesn't exist.

Inputs: path (required), target (required), content (required), port, +5 more.

ssh_editA

Replace exact text in an existing remote file over SSH — the remote counterpart of the local file-editing tool. Each edit's 'old_str' must match exactly one location in the file (as it stands after any earlier edits in the same call); ambiguous or missing matches fail without writing anything. Provide multiple {old_str, new_str} entries in 'edits' to batch several changes to the same file into a single read-then-write round trip instead of one SSH round trip per edit.

Inputs: path (required), edits (required), target (required), port, +5 more.

ssh_ensure_sessionA

Return an existing running SSH session or start a new one. This is the recommended tool for agent workflows — always provide a descriptive session_name so the session can be reliably found across tool calls and conversations. When a session is reused (reused=true in response), the cwd, env, and shell parameters are ignored — they only apply when creating a new session. Check 'created' vs 'reused' in the response to know which happened.

Inputs: target (required), cwd, env, port, +10 more.

ssh_execA

Run a one-off remote SSH command and return stdout, stderr, and exit metadata. The command runs in a non-interactive context. Use 'cwd' and 'env' for remote directory and environment setup (requires a POSIX shell on the remote). For interactive or long-running commands, use ssh_ensure_session instead.

Inputs: target (required), command (required), cwd, env, +8 more.

ssh_forwardA

Start a dedicated SSH port forward (local or remote). This is a separate tool from ssh_exec/ssh_start_session so MCP clients can permission-gate port forwarding independently. Use direction 'local' to make a remote service reachable on a local port, or 'remote' to expose a local service on the remote host.

Inputs: target (required), direction (required), local_port (required), remote_host (required), +7 more.

ssh_globA

Find remote files by name pattern over SSH — the remote counterpart of the local filename-pattern tool. Supports '', '?', '[seq]'/'[!seq]', '{a,b}' alternation, and '' for matching across multiple path segments (e.g. 'src//.ts'). A path segment starting with '.' is only matched by a pattern segment that itself starts with '.'. Enumerates under 'path' via remote find, skipping .git/.hg/.svn; matching is done locally.

Inputs: target (required), pattern (required), path, port, +6 more.

ssh_grepA

Search remote file contents over SSH — the remote counterpart of the local content-search tool. Backed by remote grep (PCRE-like -P when available, otherwise POSIX extended regex), recursing under 'path' while skipping .git/.hg/.svn. Defaults to 'files_with_matches' mode for efficiency; use 'content' mode for matching lines with line numbers and optional context.

Inputs: target (required), pattern (required), glob, path, +12 more.

ssh_list_forwardsA

List tracked SSH port forwards with their forward_id, direction, ports, target, and running status.

Inputs: target, include_stopped.

ssh_list_sessionsA

List tracked SSH sessions with their session_id, session_name, target, state, uptime, and observer details (including tmux_session_name for cross-referencing with tmux ls). Use session_name filter to find a specific named session.

Inputs: target, session_name, include_exited.

ssh_read_sessionA

Read unread output from a tracked SSH session. Set wait_seconds (e.g. 1-10) to block until new output arrives; 0 returns immediately with whatever is buffered right now. Default: 1.0. If 'truncated' is true or 'pending_output_chars' > 0, call again to drain remaining output. Check 'running' to know whether the session is still alive.

Inputs: session_id (required), wait_seconds, max_output_chars.

ssh_scpB

Copy files or directories between the local machine and one remote target via the local scp client.

Inputs: target (required), sources (required), direction (required), destination (required), +8 more.

ssh_start_sessionA

Start a new persistent interactive SSH session backed by a local PTY. Returns the session id, initial output, and observer metadata. If 'truncated' is true or 'pending_output_chars' > 0 in the response, call ssh_read_session to retrieve the remaining buffered output. For most agent workflows, prefer ssh_ensure_session instead — it reuses existing sessions and avoids accidental duplicates.

Inputs: target (required), cwd, env, port, +10 more.

ssh_stop_forwardC

Stop a tracked SSH port forward and return its final status.

Inputs: forward_id (required).

ssh_stop_sessionA

Terminate a tracked SSH session, close any attached tmux observer, and return final unread output plus exit metadata. The transcript file is preserved on disk.

Inputs: session_id (required), force, wait_seconds, max_output_chars.

ssh_syncB

Incrementally sync files or directories between the local machine and one remote target via local rsync over SSH.

Inputs: source (required), target (required), direction (required), destination (required), +11 more.

ssh_viewA

Read a remote file or list a remote directory over SSH — the remote counterpart of the local file-viewing tool. For a file, returns its content plus 'size_bytes' and 'total_lines'. Content is truncated at 20KB by default when 'view_range' isn't given and 'force_read_large_files' isn't set; use 'view_range' to page through large files instead. For a directory, returns non-hidden entries up to 2 levels deep.

Inputs: path (required), target (required), port, timeout, +7 more.

ssh_write_sessionA

Write text or a control sequence to a tracked SSH session PTY. Always terminate commands with a trailing newline (\n) to submit them. Control characters: \u0003 for Ctrl-C, \u0004 for Ctrl-D, \u001a for Ctrl-Z. Use wait_seconds (e.g. 1-5) to receive the command response in the same call. Check 'pending_output_chars' in the response; if non-zero, call ssh_read_session to drain.

Inputs: input (required), session_id (required), wait_seconds, max_output_chars.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: sessions, files, exec, transfer, and forwards are separate categories. However, ssh_start_session and ssh_ensure_session overlap significantly, and ssh_exec vs ssh_write_session could be confused without careful reading.

    Naming Consistency5/5

    All tools follow the 'ssh_<verb>[_<noun>]' pattern, using consistent snake_case. The verb comes first in every case, and nouns are attached for specific resources (sessions, forwards), while generic operations like exec, view, create, edit, grep, glob, forward stand alone. This is highly predictable.

    Tool Count5/5

    17 tools is well-scoped for an SSH server, covering sessions (6), file operations (5), transfer (2), port forwarding (3), and one-off exec (1). It is comprehensive without feeling bloated, and each tool serves a distinct need.

    Completeness4/5

    Core SSH workflows are covered: session CRUD, file read/create/edit/search, command execution, file transfer, and port forwarding. The main gap is a missing remote file delete operation, and there is no explicit tool to copy a remote file to another remote location, but these can be worked around with exec.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants full SSH/SFTP remote operations — session management, command execution, interactive shells, file transfers, port forwarding, and system diagnostics.
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server giving AI agents full SSH access with persistent sessions, structured command output, SFTP file transfer, and port forwarding.
      18
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An open MCP server that gives any AI agent SSH access to remote Linux/Unix machines — shell commands, file read/write, and SFTP transfers.
      11
      16 PyPI
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents SSH capabilities to execute commands, transfer files, and inspect remote systems through a preconfigured host list.
      93 npm
      MIT