Summary
Long-running shell work in a window you can watch.
Because every session has its own handle, an assistant can start something in one terminal, leave it running, and come back to read its output later — which is exactly what a single fire-and-forget shell call cannot do. It all happens in your own iTerm2, so you see it as it goes.
What it is
A bridge to iTerm2 on macOS. It opens terminal sessions, runs a command in a specific one, reads that session's output back, lists what is currently open, and closes a session when the work is done.
What you get
- A new terminal session opened on demand
- A command run in one addressed session rather than a shared shell
- That session's output read back
- A list of the active sessions and their details
- A session closed when it is finished with
Requirements
macOS with iTerm2 installed, since iTerm2 is macOS only, and Node to run the server. No account, no key. Input is schema-validated and each session is isolated from the others.
Setup effort
One command — npx iterm_mcp_server