termalAs of October 2026, Termius has no official MCP server — nothing built into the app, and no announcement from Termius we could find. But several community projects bridge Termius to an AI agent, and a couple of other SSH clients get you the same result a different way. Here’s each one, how it actually works, and the risk to weigh.
One disclosure up front: we build Termalin, one of the options below. We’ve tried to describe the rest as fairly as we’d want ours described, and to say where they’re the better fit.
The community bridges to Termius
Three unrelated projects share the name termius-mcp, and they work in very different ways.
- termius-mcp (MiaM1ku, on PyPI) — the one that’s
pip install-able (BSD, marked beta). A stdio server that logs into Termius Cloud: it syncs your vault, looks up a host, and runs SSH exec and SFTP. Ikaleio/termius-mcp is a close twin with the same description. Because it talks to Termius Cloud, you’re handing it your Termius login — read the code and scope it accordingly. - yapp/termius-mcp — drives the terminals in a running Termius desktop app over the Chrome DevTools Protocol. It needs Termius ≥ 10.0.6 launched with
--remote-debugging-port=9229, plus Node.js. It can create terminals, send keystrokes and keys, read output, and work the SSH sessions you already have open. The catch is that open debug port: anything local that can reach it can drive your terminals, so treat it as a development convenience, not a hardened setup. - deltaguita/termius-mcp — also drives already-open Termius tabs over CDP, but adds claim/lock guards so two agents don’t stomp on the same session.
Termius Session MCP
Termius Session MCP (ItzGlace) is a tidier take on the same idea. It shares one visible Termius terminal with an MCP client through four tools — status, sessions, read, write — and adds an MCP button inside Termius. Its defining feature is caution: every write and every output release needs in-app approval. It’s Windows only, needs Node ≥ 22, is MIT-licensed, and is explicit that it’s “an internal-API integration, not an official Termius extension” (tested against Termius 9.39.0). If you want a human finger on every step, this is the one.
A name to ignore in these searches: TerminusAI turns up alongside the others but is unrelated to Termius — it’s a generic one-tool MCP server that runs a command locally or over SSH, nothing to do with your Termius vault.
The other clients that get you there
If the real goal is “an AI agent that can work my servers,” you don’t have to stay inside Termius:
- Conduit is a connection manager for SSH, RDP, VNC and web sessions with a built-in MCP server (Apache-2.0, around 60 local tools). It’s local only — a Unix socket or Windows named pipe — so there’s no cloud endpoint, but nothing leaves your machine. Import your hosts and an agent can drive them.
- Termalin is an SSH client with its own MCP server in two shapes: 22 local tools in the desktop app, plus a hosted endpoint (
https://termal.in/mcp, 16 tools) that claude.ai, ChatGPT, Claude Code, Codex and Cursor sign into. It reaches your servers keylessly through an outbound Connector — no inbound port — applies a per-connection command policy (full, allowlist or read-only), and writes an audit log; it’s listed in the ChatGPT and Claude connector directories. Import your Termius hosts first (an~/.ssh/configexport or a CSV) and the agent works them.
The honest trade: if your hosts and habits already live in Termius and you want the lightest possible bridge, a community termius-mcp or Termius Session MCP keeps you there. If you’d rather the agent never hold a key and be able to work your servers from CI or a chat with no app running, a custodian-style client earns the cost of importing your hosts into a second app.
At a glance
| Option | How it reaches Termius hosts | Key handling | Approvals | Platforms | License |
|---|---|---|---|---|---|
| termius-mcp (MiaM1ku) | Logs into Termius Cloud | Your Termius login | — | Anywhere (Python) | BSD |
| yapp/termius-mcp | CDP into a running Termius app | Uses the app’s sessions | — | Anywhere (Node) + Termius | Unverified |
| deltaguita/termius-mcp | CDP into open Termius tabs | Uses the app’s sessions | Claim/lock guards | Anywhere (Node) + Termius | Unverified |
| Termius Session MCP | Shares one visible terminal | Uses the app’s session | Per write + per output | Windows + Termius | MIT |
| Conduit | Its own vault (import hosts) | In its AES-256 vault | — | macOS, Win, Linux, iOS | Apache-2.0 |
| Termalin | Its own MCP, local + hosted | Custodian signs; key never handed over | Per-connection policy + audit | Win, macOS, Linux, iOS (+ web) | Source-available in parts |
(“Unverified” means we couldn’t confirm the license on the repo as of October 2026.)
How to pick
- Stay inside Termius, lightest touch → a community
termius-mcp; read the code and mind the debug port. - Want a human to approve every action → Termius Session MCP (Windows only).
- One open-source app across SSH, RDP and VNC, local only → Conduit.
- Agent must run from CI or a chat with no desktop, and never hold a key → Termalin, after importing your hosts.
Termalin is a cross-platform SSH client whose built-in MCP server is a key custodian with per-connection policy and an audit log — see the MCP page, or the full Termius alternatives roundup.