Termany MCP Server

Connect Termany to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Agent-Native Terminal. The termany mcp server is what makes that connection.

What the server does

Termany keeps a large number of agent sessions in one window, tells you which session needs you, and puts the work around those sessions in the same place: diffs, worktrees, ports, remote hosts, and token cost.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Files — a file tree. Click a file to edit it in place (CodeMirror, language detection,
• Conversation — a chat pane over ACP, with its own model picker
• Browser — a webview. When a pane starts to serve a port, Termany offers to open it
• Per — pane SSH.** Each pane picks its own connection, so a local shell and two remote hosts
• Cloud — move apps/server behind auth and a container-per-session sandbox
• Variable — Default
• TERMANY_PORT — 5174 release / 5175 dev
• TERMANY_PASTE_DIR — system temp
• VITE_PTY_URL — ws://localhost:5174 release / :5175 dev
• VITE_API_URL — follows VITE_PTY_URL
• Key — Action
• Shortcuts — A starting set. All of them are rebindable in Settings → Keyboard

Credentials and setup notes

Configuration is passed through the environment: VITE_PTY_URL, VITE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Termany's toolset — Files, Conversation, Browser and 10 more — is a fair guide to whether it matches your workflow. It is maintained by thinkany-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Termany's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Termany.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.