termcp

Termcp: the final MCP | Terminus MCP

With Termcp:

• An AI can install and use any number of MCP servers, dynamically, at run time.

• An AI can write its own MCP server and hot-load it.

• An AI can use SSH to manage hosts, approved and collaborated on by a human.

• An AI can install and call MCP servers across machines over nothing but SSH.

Exactly one tool is exposed. Built on the Termcp protocol (Terminalization Model Context Protocol): loading more MCP servers and skills does not grow the context.

A single dependency-free binary (10 MB+), cross-platform, with a WYSIWYG web UI where a human and an AI share the same terminals and collaborate.

Related MCP server: shell-session-mcp

Install

0 · AI install

Install npx -y @open-mcp-ai/termcp daemon stdio as an MCP named termcp.

Copy this to the AI.

1 · One command per agent

2 · Config file

{
  "mcpServers": {
    "termcp": {
      "command": "npx",
      "args": ["-y", "@open-mcp-ai/termcp", "daemon", "stdio"]
    }
  }
}

The npm wrapper downloads the matching prebuilt binary (override with TERMCP_VERSION, TERMCP_MIRROR, TERMCP_BIN, TERMCP_SKIP_DOWNLOAD). Flags: docs/cli.md. Docker recipes, Compose and a token-free loopback setup: docs/deploy.md.

HTTP transport, when an instance is already answering somewhere (npx -y @open-mcp-ai/termcp):

{
  "mcpServers": {
    "termcp": {
      "type": "http",
      "url": "http://localhost:18765/stream"
    }
  }
}

Reachable from a client in Docker as http://host.docker.internal:18765/stream (macOS/Windows) or the host's LAN IP; from another container on the same network as http://termcp:18765/stream. Legacy SSE uses http://localhost:18765/sse — only /sse, JSON-RPC goes to /message by itself. With --auth-token, add a bearer header: "headers": {"Authorization": "Bearer <token>"}.

Docs

Benchmark

Comming Soon

Functional security testing

Comming Soon

Star History

License

Released under the MIT License. Thanks to friends in the linux.do community for the discussions, feedback, and support.