pty-mcp runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 22 Oct 2026.
Interactive PTY sessions over MCP: local shells, SSH, serial ports, and persistent remote sessions.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
if keyPath := ssh_config.Get(host, "IdentityFile"); keyPath != "" && keyPath != "~/.ssh/identity" {
if keyPath := ssh_config.Get(host, "IdentityFile"); keyPath != "" && keyPath != "~/.ssh/identity" {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to pty-mcp
same job, measured the same wayPersistent stateful remote SSH sessions for AI agents via MCP + OpenSSH.
MCP server for real interactive terminal sessions — REPLs, SSH, databases, Docker
MCP server for interactive terminal sessions — SSH, REPLs, database CLIs, TUI apps
Local MCP control plane for persistent sessions and compact capability discovery.
Lightweight MCP server providing terminal access (SSH & local shells) for AI assistants.
Persistent memory for AI agents — log and recall conversation context over MCP.
Stateful, structured, safe shell sessions for AI agents over local, SSH, and Docker.
Local-first, persistent memory for AI coding agents — remember, recall, forget, and list, over MCP.
pty-mcp — questions
Answers built from our own checks of this server.