MokoSSH MCP Server

mcp-mokossh is a Model Context Protocol (MCP) server that turns SSH into a first-class capability for your AI assistant — letting Claude Code and other MCP clients run commands, move files, manage databases, take backups, and monitor health on your remote servers, all through your existing SSH keys. Install it in seconds with npm install -g @mokoconsulting/mcp-mokossh, point it at your servers with a few environment variables, and drive real DevOps work in plain language from the assistant you already use. It ships 37 tools across six groups, so everyday operations — deploy a file, dump a database, check a service — become a single request instead of a terminal session.

What it is

mcp-mokossh (npm package @mokoconsulting/mcp-mokossh, version 3.6.0) is a Node.js MCP server for SSH remote-server management. It exposes 37 tools across six groups — Core, Database, Backup, Monitoring, Deployment, and Automation — that let an MCP-capable AI assistant execute commands (including sudo), transfer files, run database operations, create and restore backups, monitor server health, and automate DevOps workflows over SSH.

Rather than scripting SSH by hand, you register the server once with your MCP client and the assistant can then operate your fleet conversationally: "back up the CRM database", "deploy this file to the web server", "is nginx healthy on the git host?" Authentication uses your standard SSH keys (or a password), so no new credential system is introduced. Tool availability is configurable, letting you enable only the operations you want exposed.

The package is a Moko Consulting fork of the upstream bvisible/mcp-ssh-manager project, maintained on MokoGIT.

Install (npm)

These packages are published to public npm under the @mokoconsulting scope. Install globally (this also provides the ssh-manager CLI):

npm install -g @mokoconsulting/mcp-mokossh

Or run it on demand with npx, no install required:

npx -y @mokoconsulting/mcp-mokossh

Requires Node.js 20 or newer. Optionally, you can pull the package from the MokoGIT registry mirror by adding this scope-to-registry mapping to your .npmrc:

@mokoconsulting:registry=https://git.mokoconsulting.tech/api/packages/MokoConsulting/npm/

The global install exposes three binaries: mcp-mokossh and ssh-mcp (the MCP server) and ssh-manager (a CLI for managing tool enablement, aliases, and hooks — for example ssh-manager tools).

Configure

Register the server with your MCP client (such as Claude Code) by adding it to your mcpServers config. The server reads its server list from environment variables using the pattern SSH_SERVER_<NAME>_*, where <NAME> is a label you choose (uppercase). At minimum, each server needs a _HOST and _USER, plus a _KEYPATH (recommended) or _PASSWORD:

{
  "mcpServers": {
    "mokossh": {
      "command": "npx",
      "args": ["@mokoconsulting/mcp-mokossh"],
      "env": {
        "SSH_SERVER_WEB_HOST": "web.example.com",
        "SSH_SERVER_WEB_USER": "root",
        "SSH_SERVER_WEB_KEYPATH": "~/.ssh/id_ed25519",
        "SSH_SERVER_WEB_PORT": "22",
        "SSH_SERVER_WEB_DEFAULT_DIR": "/var/www"
      }
    }
  }
}

Define as many servers as you need by repeating the block with different <NAME> labels (for example SSH_SERVER_GIT_HOST, SSH_SERVER_CRM_HOST). Per-server variables the server recognizes include:

• SSH_SERVER_<NAME>_HOST — hostname or IP (required)
• SSH_SERVER_<NAME>_USER — SSH username
• SSH_SERVER_<NAME>_KEYPATH — path to a private key (recommended auth)
• SSH_SERVER_<NAME>_PASSWORD — password (alternative to key auth)
• SSH_SERVER_<NAME>_PASSPHRASE — passphrase for the key
• SSH_SERVER_<NAME>_PORT — SSH port (defaults to 22)
• SSH_SERVER_<NAME>_DEFAULT_DIR — default working directory
• SSH_SERVER_<NAME>_SUDO_PASSWORD — password for sudo operations
• SSH_SERVER_<NAME>_DESCRIPTION — free-text label
• SSH_SERVER_<NAME>_PLATFORM — platform hint
• SSH_SERVER_<NAME>_PROXYJUMP / SSH_SERVER_<NAME>_PROXYCOMMAND — jump-host / proxy settings

Configuration can also be supplied via a .env file in the working directory, or a TOML file pointed to by SSH_CONFIG_PATH. Precedence, highest to lowest: environment variables, then .env, then the TOML config.

Tooling

The 37 tools are organized into six groups:

• Core — command execution, sudo command execution, and file upload/download. The everyday building blocks for running shell commands and moving files to and from a server.
• Database — run queries, dump (export) and import databases, and list available databases. Handy for MySQL/MariaDB-backed apps such as Joomla and Dolibarr sites.
• Backup — create, list, restore, and schedule backups of files and databases.
• Monitoring — health checks, service status, and process management, so the assistant can verify a host is healthy or inspect and manage running processes.
• Deployment — deploy files to remote servers with permission handling built in.
• Automation — server aliases, command aliases/shortcuts, and automation hooks that trigger around operations.

Beyond these groups, the server includes supporting capabilities such as SSH key management, interactive session handling, SSH tunnel management, and server grouping for multi-host operations. Which tools are active is controlled through the tool-enablement configuration, managed with the ssh-manager CLI (for example, ssh-manager tools).

Get help

Need a hand getting mcp-mokossh installed, configured, or connected to your assistant? Open a support ticket with Moko Consulting, or call us at (931) 279-6313.