termius-mcp

MCP server that drives visible terminals in a running Termius app.

Local only. This server connects to a locally running Termius desktop app via the Chrome DevTools Protocol on localhost:9229.

Prerequisites

Termius must be running with remote debugging enabled. On macOS:

/Applications/Termius.app/Contents/MacOS/Termius --remote-debugging-port=9229

At least one Termius window must be open. The server connects to the primary renderer (the main Termius UI), injects a bridge that exposes the Termius mediator API, and registers MCP tools that call into that bridge.

Related MCP server: Terminal MCP

Quick Start (with an MCP client)

Install once globally, or use npx to always run the latest version without install:

npx -y termius-mcp

Then wire it into your MCP client. Pick your client below.

Claude Desktop / Claude Code

~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows:

{
  "mcpServers": {
    "termius-mcp": {
      "command": "npx",
      "args": ["-y", "termius-mcp"]
    }
  }
}

On Windows, Claude Desktop needs the cmd /c wrapper:

{
  "mcpServers": {
    "termius-mcp": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "termius-mcp"]
    }
  }
}

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in the repo for project-scoped):

{
  "mcpServers": {
    "termius-mcp": {
      "command": "npx",
      "args": ["-y", "termius-mcp"]
    }
  }
}

opencode

Add to your opencode.json / opencode.jsonc:

{
  "mcp": {
    "termius-mcp": {
      "type": "local",
      "command": ["npx", "-y", "termius-mcp"]
    }
  }
}

Cline (VS Code)

cline_mcp_settings.json:

{
  "mcpServers": {
    "termius-mcp": {
      "command": "npx",
      "args": ["-y", "termius-mcp"]
    }
  }
}

From source (for development)

git clone https://github.com/yapp/termius-mcp.git
cd termius-mcp
npm install
npm start

A repo-root .mcp.json is provided so Cursor / Claude Code / VS Code MCP builds can auto-discover the server without writing the config by hand.

Usage

Once connected, ask the client to:

1. Open a local terminal in Termius (terminal_create).

2. Send a command to it (terminal_send).

3. Read the output (terminal_read).

The initial CDP connection is non-fatal. If Termius is not running when the server starts, the next tool call retries the connection.

Tools

Local terminals

Existing SSH saved-host sessions

These tools operate on terminals that already exist in the running Termius app, typically SSH saved-host sessions opened from the UI. They auto-sync the bridge with the Redux state, so SSH terminals whose .terminal DOM element is not mounted (hidden tabs) remain addressable by terminalId. No credentials are needed: the bridge piggybacks on Termius's already-authenticated session.

Configuration

Testing

Smoke test against a running Termius instance (exercises list, create, send, read, resize, sendKeys):

npm run smoke

End-to-end test that creates terminals, sends commands, and reads output:

npm test

Both require Termius running with --remote-debugging-port=9229.

Requirements

• Node.js with ESM support

• Termius desktop app (developed against v10.0.6)

• Network access to localhost:9229