Tamio MCP

A native macOS SSH client with a built-in MCP server: agents run commands on your servers only after you approve them.

  • 137 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • The agent runs commands on your servers and edits servers, keys and port forwards.
  • An always-allow grant removes approval for the chosen agent.
All reasons and checks

missuo/tamio

Install

Manual install

brew install --cask owo-network/brew/tamio

The command from the README. Then in Claude Code: `claude mcp add tamio -- /Applications/Tamio.app/Contents/Resources/tamio-mcp`.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The agent runs commands on your servers and edits servers, keys and port forwards.
  • An always-allow grant removes approval for the chosen agent.

This is third-party code. Review the repository files before installing.

What it does

Tamio combines an SSH client on the Ghostty terminal engine, dual-pane SFTP, live server status and end-to-end encrypted iCloud sync. The built-in `tamio` MCP server gives agents the server list with load (CPU, memory, disk, traffic), runs commands and saved snippets on one or many servers, and edits servers, keys and port forwards. Every agent command waits for your decision: once, for an hour or always. The agent never receives passwords or private keys; for an added key it sees only the public half. Actions are logged per server (which agent, what it ran, what came back), and the next agent reads that through `get_activity`. The server listens on a Unix socket that only your user can open.

Who it is for. Admins and developers on macOS who run a fleet of servers over SSH and want to hand routine work to Claude Code or Codex under control.

Good fit when

  • An agent updates packages on a group of servers and you approve each command.
  • You switch agents and need to keep the history of what was done on a server.
  • Servers live in an SSH client with keys in Keychain and you do not want to export keys.
  • You need host load and state for the agent decision before a deploy.

Not a fit when

  • You work on Linux or Windows: the app needs macOS 14 or newer.
  • The agent must run unattended and an "always allow" approval is unacceptable.
  • You need an MCP for servers without a separate client app.

Example request

Show the load on every server in the web group, propose a package update and run it on one server after my approval.

MCP

Transport
stdio
Authentication
not required

Limitations

The project is in early development and the iOS version is only planned. The app must be running with MCP enabled in settings, and the `tamio-mcp` binary path is set by hand for Codex and other clients. "Always allow" removes approval for the chosen agent. iCloud sync is on by default and can be turned off in settings. From the MCP point of view command execution on servers is irreversible: read the exact command text and target server before approving.

How to disable. Turn off the MCP server in the MCP section of settings, remove the `tamio` entry from the client config (`claude mcp remove tamio`) and revoke always-allowed agents. Uninstall the app as usual and disable iCloud data separately.

FAQ

Does the agent see passwords and keys?

No. No tool returns a password, private key or passphrase. For a new key the agent gets only the public half.

How do I connect Codex?

Add a `[mcp_servers.tamio]` section to `~/.codex/config.toml` with `command` pointing to `/Applications/Tamio.app/Contents/Resources/tamio-mcp`.

What about network access?

The MCP server listens on a Unix socket only your user can open and uses no network port.

What does per-task history mean?

The agent names the goal of a step, such as "Install nginx", and all steps toward it are kept as one entry with results. The next agent sees the outcome at a glance.

How do I install and update?

Through Homebrew with `brew install --cask owo-network/brew/tamio`, or a disk image from Releases. The app updates itself through Sparkle.

Discussion

No questions or reviews yet.

MCP SSH Agent is an MCP server that reads hosts from ~/.ssh/config, runs commands and copies files through system ssh and scp.

MCP serverBroad access105Repository stars

A native macOS terminal built on Ghostty with vertical tabs and notifications when an agent needs your input

CLIBroad access28.8KRepository stars

TMX is a desktop SSH client with terminals, SFTP and a built-in MCP server through which an agent drives sessions.

MCP serverBroad access102Repository stars

An SSH MCP server: the agent runs commands, reads and writes files over SFTP, transfers files and starts long jobs while credentials stay with you

MCP serverBroad access1KRepository stars

Muxin MCP connects an agent to your computers, with remote sessions that keep running after the application window closes.

MCP serverBroad access462Repository stars

A command-line SSH tool for agents: remote execution, file upload and download, and command allow and block lists.

CLIBroad access88Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
Tamio (this card)nonot required137
MCP SSH ManagernoAPI key539a standalone SSH MCP server with a vault and audit trail; Tamio is built into a macOS graphical client with SFTP and a terminal
SSH MCPnoAPI key875a minimal MCP for controlling Linux servers over SSH; Tamio adds approvals, per-server history and live metrics

README in short

MCP features, a security section, terminal and SFTP, iCloud sync, Homebrew install, building from source and tests.

README badge

Report a problem