Give Claude SSH access to your servers — from the chat.

01  /  set up in 3 steps

Connect claude.ai to your servers in three steps.

The connector is Termalin’s hosted MCP endpoint — it reaches servers you’ve enrolled with a Connector, a one-line agent that dials out from the box. You need a Termalin account on Pro (or the trial) and at least one enrolled server.

• 1Enroll a server. Sign in at termal.in/account, click Add Connector, and run the one-line install command it gives you on a box you manage. From then on it’s reachable keylessly, with no inbound port. More on how that works: the Connector.
• 2Add the connector. In claude.ai, open Termalin’s listing in the connectors directory and click Connect — from the chat that’s Settings → Connectors → Browse connectors. Prefer to add it by URL? Use Settings → Connectors → Add custom connector and paste:

https://termal.in/mcp

• 3Approve and ask. Claude opens Termalin’s sign-in page; sign in with your termal.in account and approve. Now hosts_list, ssh_exec, the sftp tools and generate_password are in the chat — try “Are all my servers online? Anything that needs attention?”

Requirements first-timers miss: a paid plan or the trial, at least one Connector online, and a verified email. A host that only exists in the desktop app isn’t enrolled — the chat won’t see it until you run the Connector on it.

02  /  claude code & claude desktop

On your machine? Use the local server.

The connector above is for the chat at claude.ai. When Claude runs on your own machine, point it at the bundled termalin-mcp binary instead — it reaches the hosts you export in Settings → MCP, authenticated through Termalin’s key custodian.

• ▸Claude Code — one command, then it’s live. There’s a full Claude Code setup guide.

claude mcp add termalin -- <path>/termalin-mcp

• ▸Claude Desktop — add Termalin to its MCP config:

{
  "mcpServers": {
    "termalin": { "command": "<path>/termalin-mcp" }
  }
}

The local server has more tools than the hosted connector — persistent sessions, port forwards and live-terminal control on top of commands and files. See the full tool reference for what each surface carries.

03  /  oauth, not keys

Why this isn’t “pasting a key into a chatbot”.

The connector never touches SSH credentials, because there are none to touch:

• ▸OAuth, not keys. Claude gets a scoped token from Termalin’s sign-in page — no API key to paste, no private key in the context window. It’s the standard MCP authorization flow.
• ▸Keyless reach. Your servers connect outward through Connectors, and each run authenticates with a short-lived certificate. No inbound port, no stored key.
• ▸Only your servers. A token is bound to your account and reaches your enrolled servers — not whatever it could route to.

04  /  audited & revocable

Everything on the record. Revoked in one click.

Every approval and every command Claude runs lands in your account’s activity trail, so “what did it do on prod?” has an answer you can read. And access is never a standing grant: your account page lists connected AI apps under “AI apps”, and Disconnect kills that app’s tokens instantly — with no key to rotate afterward. The custody model behind all of it is on SSH for AI agents.

05  /  where the edges are

Honest limits, so you know what you’re getting.

• ▸Non-interactive commands. Each command runs in its own session — cd doesn’t persist between calls, and full-screen programs (vim, htop) won’t fly. Agents handle this by chaining commands.
• ▸Time-boxed and capped. Commands are time-boxed (up to 300 s) and file operations are text-only, capped at 512 KB. For big or binary transfers, use the app.
• ▸Enrolled servers only. The connector reaches servers running a Connector. For hosts you only have in the desktop app, the local server covers that side — and it works with ChatGPT, Cursor and Codex too.