Reminal MCP
Your machine's terminal, windows and desktop in a browser, plus an MCP server for agents to read and type into other sessions
- 309 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- The `send_keys` tool types into a live shell on any enrolled machine, so the agent acts with your user's rights
- Install runs a `curl ... | sh` script from the main branch and puts a binary in your home directory
- `reminal expose` traffic is readable by the relay: it has no end-to-end encryption
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/harshalgajjar/Reminal/main/install.sh | shFor macOS and Linux. Read the script before running it: it puts the binary in ~/.local/bin. The README has a PowerShell variant for Windows.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The `send_keys` tool types into a live shell on any enrolled machine, so the agent acts with your user's rights
- Install runs a `curl ... | sh` script from the main branch and puts a binary in your home directory
- `reminal expose` traffic is readable by the relay: it has no end-to-end encryption
This is third-party code. Review the repository files before installing.
What it does
Reminal is a single Go binary. It opens the terminal, application windows and the full desktop of your machine in any browser. The machine dials out to a relay on Cloudflare, so it has no open ports. Access rests on a session ID and a PIN, and the two sides use AES-256-GCM encryption. The browser receives window and desktop video directly over WebRTC, bypassing the relay. For agents, the `reminal integrate` command registers the `reminal mcp` server with every agent CLI it finds: Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Antigravity, Amp and others. For pi it installs a native extension. The server exposes four tools: `list_sessions` shows sessions on this and other enrolled machines, `search_sessions` runs a regular expression over live terminal output, `read_transcript` reads another session's terminal as text, and `send_keys` types into it. An agent on a laptop can therefore watch an agent on a build server and answer it, even when the agents come from different vendors. The `add_note` tool pins a note to a window and delivers it to your phone. The same capabilities work without MCP: hand an agent a session ID and a PIN, and it connects like any other viewer.
Who it is for. People who run agents on several machines (a laptop, a build server, a home Mac) and want to watch them and answer from a phone or from another agent.
Good fit when
- An agent on a build server waits for confirmation while you are away: the answer goes from your phone through the browser
- Claude Code on a laptop reads the test output of a Codex session on another machine
- You need to show a colleague a live terminal without SSH keys or port forwarding: ID and PIN travel by separate channels
- A long task runs on a Mac and you have left: closed-lid mode works on macOS, everything else on all three systems
Not a fit when
- The machines are someone else's or shared: `send_keys` types real keystrokes into a shell, so connect only your own
- The machine must stay without outbound connections: Reminal dials out to the Cloudflare relay
- Plain SSH is enough: keys and an open port are already set up, and a second channel is unnecessary
- You only need to move a file: `reminal copy` and `reminal paste` work on their own, no MCP required
Example request
List the sessions open on my machines and read the last forty lines of the terminal on the build serverMCP
- Transport
- stdio
- Authentication
- not required
Limitations
- The relay runs on Cloudflare. You can host your own if you would rather not rely on someone else's infrastructure.
- Closed-lid mode exists on macOS only. Source builds on macOS need a Swift helper for window and desktop capture.
- You enroll your own machines with `reminal own`, which prints the device ID, and run `sudo reminal add owner <id>` on each machine. Without it, every session asks for a PIN.
- The license is AGPL-3.0. Embedding in a product falls under a separate commercial license.
- On Windows, sessions open PowerShell 7, then Windows PowerShell, then cmd. The terminal runs through ConPTY.
How to disable. `reminal integrate --remove` unregisters the MCP server from all agents. Ctrl+C closes a session, and its ID and PIN stop working at once. The binary sits in ~/.local/bin/reminal on macOS and Linux and in %LOCALAPPDATA%\Programs\reminal on Windows.
FAQ
How do I connect Reminal to Claude Code?
Install the binary and run `reminal integrate`: it finds Claude Code, Codex, Cursor and other agent CLIs and registers the MCP server with them. You can start the server by hand with `reminal mcp` over stdio. `reminal integrate --remove` undoes the registration.
Can the relay see my terminal?
No, terminal, window and desktop data cross the relay as AES-256-GCM ciphertext. The exception is `reminal expose`: forwarded ports pass without end-to-end encryption and only a PIN protects them. You can host the relay yourself.
Can I drive an agent without MCP?
Yes. Give the agent a session ID and a PIN, and it connects like any other viewer to every machine you shared.
How is Reminal different from SSH?
Reminal opens no port on the machine and needs neither a static IP nor permanent keys. The machine dials out to the relay and a browser serves as the client. Access rests on an ID and a PIN that vanish after Ctrl+C. SSH uses permanent keys and port 22.
Which systems does Reminal support?
macOS, Linux and Windows, including Windows ARM64. On macOS both Apple Silicon and x86_64 work. The binary installs without sudo into ~/.local/bin on macOS and Linux and into %LOCALAPPDATA%\Programs\reminal on Windows.
Discussion
No questions or reviews yet.
Related
MCP serversMuxin MCP connects an agent to your computers, with remote sessions that keep running after the application window closes.
A secure MCP runtime through which an agent operates local machines, servers and containers
Tmux MCP Server: agent access to tmux sessions
Tmux MCP Server
An MCP server that lets an agent read tmux panes, run commands in them and create sessions while you watch the output
A WebSSH console for VPS with an MCP server: the agent works across several servers while ACL tokens limit tools and hosts.
Containarium: isolated boxes for AI agents
Containarium
A platform on your own server that gives each agent its own Linux box with SSH and MCP tools for commands and files
Native macOS terminal with an MCP server and CLI: agents see panes, commands and output, and you grant permissions in one window
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Reminal (this card) | no | not required | 309 | |
| Tmux MCP Server: agent access to tmux sessions | no | not required | 306 | works with tmux sessions on one machine, while Reminal spans several machines and application windows |
| Remote macOS Use: control of a remote Mac | no | API key | 491 | controls a remote Mac through MCP, while Reminal serves a terminal and desktop in the browser on three systems |
README in short
The page opens with a one-line install and a list of scenarios: a terminal in the browser, window and desktop control, a public address for a local port, file transfer and shared access by ID and PIN. A security section, a comparison with SSH and a command table follow.