Hex SSH
Let your coding agent run remote shell, file, and tmux work over SSH without flooding the chat with duplicate file dumps.
Overview
Hex SSH is an MCP server for the Operate phase that gives coding agents token-efficient SSH access with hash-verified files and persistent tmux sessions across 14 tools.
What is this MCP server?
- 14 MCP tools for SSH workflows with a token-efficient design
- Hash-verified file transfers so agents confirm content without re-reading whole files
- Persistent tmux sessions for long-running remote commands and attach/resume flows
- stdio npm package @levnikolaevich/hex-ssh-mcp (v1.9.2) for local MCP hosts
- Suited to solo builders who manage VPS, bare metal, or homelab targets from Claude Code or Cursor
- Server version 1.9.2
- Transport: stdio via npm package @levnikolaevich/hex-ssh-mcp
Community signal: 488 GitHub stars.
What problem does it solve?
Remote debugging and deploy fixes over SSH burn context tokens when agents repeatedly read and echo whole files and lose state when one-shot shell commands end.
Who is it for?
Solo builders who SSH into their own VPS or staging boxes and want Claude or Cursor to operate shells and files there reliably.
Skip if: Teams that only deploy via managed PaaS with no SSH, or anyone who needs a full CI/CD or secrets vault instead of an SSH tool layer.
What do I get? / Deliverables
Your agent can run verified file ops and durable tmux sessions on remote hosts with less redundant output cluttering the conversation.
- Agent-callable SSH and tmux operations on configured remote machines
- Hash-verified remote file workflows with fourteen dedicated MCP tools
Recommended MCP Servers
Journey fit
Remote servers and sessions are a daily concern once something is live or staging exists, which maps to running production infrastructure from the agent. SSH, tmux, and verified file sync are core infra operations for deploys, debugging hosts, and keeping long-running jobs attached.
How it compares
SSH remote-execution MCP, not a cloud provisioner or a local terminal skill.
Common Questions / FAQ
Who is Hex SSH MCP for?
Indie and solo developers who manage servers over SSH and want their AI agent to run remote commands, sync files with hash checks, and keep tmux sessions without wasting tokens.
When should I use Hex SSH MCP?
Use it during operate and ship follow-ups when you need the agent on a live or staging host—for deploy fixes, log investigation, config edits, or long-running jobs in tmux.
How do I add Hex SSH MCP to my agent?
Install the npm package @levnikolaevich/hex-ssh-mcp, register it as a stdio MCP server in Claude Code, Cursor, or your client, and configure SSH credentials or keys your environment already uses for the target host.