Termcp: MCP server, setup and security

What Termcp does

According to its repository: “An MCP server that lets AI agents act like a human at a real terminal, local or over SSH.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Termcp is listed under Terminal and OS, a category of 115 servers in the directory, where it ranks #85 by stars.

Topics declared by the repository: ai-agents, go, pty, ssh, agents, interactive.

Installing and connecting Termcp

Distribution modes declared in the official MCP registry:

• Docker (OCI) image

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Go.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

Points found for Termcp:

• System access: the Terminal and OS category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on May 5, 2026, the open-mcp-ai/Termcp repository has 57 stars and 12 forks, with 30 open issues. It has more stars than 54% of the servers in the directory. It received changes this month. Version published in the registry: 0.2.7 (October 9, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.