Termix MCP Server

An MCP server that lets Claude (or any other MCP client) talk to a self-hosted Termix instance — the open-source SSH client / server-management tool — via its REST API.

This is a community/unofficial project, not affiliated with the Termix team.

What it can do

Related MCP server: MCP SSH Tools Server

Requirements

• Node.js 18+

• A running, self-hosted Termix instance (see the Termix install docs)

• A Termix API key: log into Termix, go to User Profile -> API Keys, and create one. (JWT bearer tokens also work, but API keys are simpler for automation and can be scoped/expired independently of a login session.)

Setup

git clone <your-fork-url> termix-mcp
cd termix-mcp
npm install
cp .env.example .env
# edit .env and fill in TERMIX_BASE_URL and TERMIX_API_KEY

TERMIX_BASE_URL is the base URL of the Termix backend API, not the web UI — check the docs for your deployment (for a default local Docker install this is typically http://localhost:30001; adjust if you've changed ports or are running behind a reverse proxy).

Run it directly

npm start

The server communicates over stdio, so it's meant to be launched by an MCP client (Claude Desktop, Claude Code, etc.), not run standalone in a terminal for interactive use.

Configure in Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "termix": {
      "command": "node",
      "args": ["/absolute/path/to/termix-mcp/src/index.js"],
      "env": {
        "TERMIX_BASE_URL": "http://localhost:30001",
        "TERMIX_API_KEY": "your_termix_api_key_here"
      }
    }
  }
}

Restart Claude Desktop afterwards.

Configure in Claude Code

claude mcp add termix -- node /absolute/path/to/termix-mcp/src/index.js

Then set TERMIX_BASE_URL / TERMIX_API_KEY in your shell environment or in the MCP server config, per the Claude Code docs.

Notes & caveats

• This was built from the public Termix API reference at https://docs.termix.site/api/termix-api. Most endpoints used here (SSH hosts, statuses, metrics, tunnels, activity) were verified directly against that reference. A few (Docker session establishment, alerts, and the exact create_ssh_host/update_ssh_host body schema) are inferred from naming conventions and REST patterns and were not individually confirmed — check the live docs for your Termix version before relying on them in production, and adjust src/termix-client.js if a path or body shape has changed.

• create_ssh_host accepts a free-form JSON object for the host body because the schema varies a lot depending on auth type (password, key, credential reference, Tailscale, etc.) — see the Termix docs / JSON import format page for the full field list.

• Destructive tools (delete_ssh_host, disconnect_ssh_tunnel, container stop/restart) are exposed as regular tools with no extra confirmation step built in — if you're wiring this into an agent that acts autonomously, consider gating those in your client/agent policy.

• No pagination/filtering helpers are included; responses are returned as-is from the Termix API.

Extending

Add new endpoints in two steps:

1. Add a method to termix in src/termix-client.js that calls termixRequest(method, path, { query, body }).

2. Register a server.tool(...) in src/index.js that calls it.

The full Termix API surface (100+ operations covering credentials, RBAC, snippets, file manager, users/OIDC, etc.) is documented at https://docs.termix.site/api/termix-api if you want to add more tools.

License

MIT — see LICENSE.