Termcp

io.github.open-mcp-aiPublished by GitHub account open-mcp-aiv0.2.8Updated Oct 27, 2026

An MCP server that lets AI agents act like a human at a real terminal, local or over SSH.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

MCP server that gives an AI agent a real terminal, local or over SSH, exposing a single tool for running commands and managing hosts.

What you can do
  • Run commands in real terminals, local or over SSH, as a human would
  • Install, write and hot-load additional MCP servers and skills at run time
  • Manage hosts and call MCP servers across machines over SSH
  • Share the same terminals with a human through a web UI
When to use it
Useful when an assistant needs to operate a shell rather than call narrow APIs: installing or wiring up other MCP servers, running commands on remote hosts over SSH, or working alongside a human in shared terminal sessions.
Requirements
Runs as a local process, typically via npx with the daemon stdio subcommand, or as a Go install, Docker image or prebuilt binary. An HTTP transport is available when an instance is already running. Docker deployments set TERMCP_AUTH_TOKEN; with --auth-token, clients send a bearer Authorization header.
Before you install
The assistant gets shell access, so it can run arbitrary commands, change or delete data, and act on remote hosts over SSH. It can also install and hot-load other MCP servers, which widens what it can do. Docker examples set TERMCP_AUTH_TOKEN, so use a long random secret and keep the HTTP endpoint off untrusted networks.

Installation

In SourceWeft

  1. Open Termcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[header banner]

[Termcp logo]

⚡ Termcp

[Termcp tagline]

[Stars] [Forks] [Release]

[Platform] [Pure Go, No CGO] [MIT License]

English | 中文

[Install] [Docs] [Website]

[divider]

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.

[Termcp extensions panel: which MCPs are installed, which host each one runs on, and whether it is available]

Install 80+ MCP servers and skills.

[Termcp console: local and SSH sessions on one screen, every line marked human / AI / shell output]

Host management.

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

AgentCommand
Claude Codeclaude mcp add termcp -- npx -y @open-mcp-ai/termcp daemon stdio
Codexcodex mcp add termcp -- npx -y @open-mcp-ai/termcp daemon stdio
Gemini CLIgemini mcp add termcp npx -- -y @open-mcp-ai/termcp daemon stdio

2 · Config file

json
{  "mcpServers": {    "termcp": {      "command": "npx",      "args": ["-y", "@open-mcp-ai/termcp", "daemon", "stdio"]    }  }}
Other install methods — npm / Go / Docker / prebuilt binary
Command
npmnpm i -g @open-mcp-ai/termcp — installs a termcp command; with it, drop npx -y @open-mcp-ai/termcp from every snippet above and use termcp. Wrapper: open-mcp-ai/Termcp-npm.
Gogo install github.com/open-mcp-ai/termcp@latest — GOPROXY=https://goproxy.cn,direct in mainland China; also usable as a module (go get github.com/open-mcp-ai/termcp).
Dockerdocker run -d --name termcp -p 18765:18765 -v termcp-data:/home/termcp -e TERMCP_AUTH_TOKEN=change-me-to-a-long-random-secret ghcr.io/open-mcp-ai/termcp:latest termcp --no-internal --host 0.0.0.0 --port 18765
BinaryPrebuilt releases — linux / darwin / windows on amd64 / arm64, one static file each.

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):

json
{  "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

docs/cli.mdEvery flag and subcommand, capability gates, authentication.
docs/clients.mdAll four entrances end to end: MCP transports, the stdio bridge, authentication, REST examples, and the one-tool surface.
docs/deploy.mdDocker, multi-stage builds, Compose, pure-API build.
docs/protocol.mdTERM/1 specification: wire format, status codes, headers, the 19 directives, the three gates.
docs/capabilities.mdThe full capability surface and the security model.
docs/api.mdREST endpoints, WebSocket frames, locator resolution.
docs/capabilities.mdFull capability surface and the security model.
docs/architecture.mdSession kernel, entrances, storage.
docs/design/Design records: Web UI, resource model, session storage, font stack, mobile terminal.
CHANGELOG.mdRelease notes.

Benchmark

Comming Soon

Functional security testing

Comming Soon

Star History

[Star History Chart]

License

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

[footer]

Source: README.md at commit 0595cb5

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

9
  1. v0.2.8LatestOct 26, 2026
  2. v0.2.7Oct 9, 2026
  3. v0.2.6Oct 7, 2026
  4. v0.2.5Oct 1, 2026
  5. v0.2.4Sep 29, 2026
  6. v0.2.3Sep 26, 2026
  7. v0.2.2Sep 25, 2026
  8. v0.2.1Sep 20, 2026
  9. v0.1.17Sep 19, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts