close-terminal
Close a specific terminal
LABSCO 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
USE CASES
01
Watching a long build instead of blocking on it
Open a session, start the build in it, and read the output when you come back rather than waiting on one call.
02
Running two things side by side
Open a second session for the server while the first runs the tests, and keep track of which is which.
03
Picking up a session you started earlier
List what is still open and read the output of the one you left running.
04
Clearing up after a task
Close the session you finished with, so the next question is not answered against a stale terminal.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
execute-command
Execute a command in a specific terminal
list-terminals
List all active terminals and their information
open-terminal
Open a new terminal instance
read-output
Read the output from a specific terminal
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
Requires
- npx on PATH
- Node.js >= 14.x
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"iterm_mcp_server": {
"command": "npx",
"args": [
"iterm_mcp_server"
]
}
}
}npx
TERMINAL
npx iterm_mcp_server
