iTerm MCP for Claude

Safety notes

iTerm MCP gives Claude direct access to the active iTerm2 terminal session.
The README states that the server has no built-in command safety restrictions and does not evaluate command risk.
The write_to_terminal tool can run shell commands, paste multiline input, interact with REPLs, trigger builds, modify files, start network tools, or run destructive commands.
The send_control_character tool can send Control-C, Control-Z, Escape, telnet escape, and other control characters that interrupt or alter running processes.
The source uses AppleScript through osascript to write text to iTerm2, read the active session buffer, retrieve the TTY, and send control characters.
The model may not know whether a command succeeded until it reads terminal output, and the README expects the user to monitor and abort when needed.

Privacy notes

Terminal output can expose secrets, API keys, tokens, environment variables, shell history, prompts, hostnames, usernames, file paths, git remotes, logs, stack traces, credentials, and local project data.
Commands typed by Claude may be stored in shell history, terminal scrollback, logs, audit systems, or process histories.
Reading the active session buffer may reveal unrelated work already visible in iTerm2.
Do not use this server in terminals connected to production systems, customer data, privileged shells, or secret-bearing sessions unless that exposure is approved.

Prerequisites

macOS with iTerm2 running.
Node.js 18 or newer available to the MCP client runtime.
macOS Automation and accessibility permissions reviewed for controlling iTerm2.
Active iTerm2 tab selected intentionally before allowing Claude to use the server.
Human supervision and an abort plan for multi-step terminal tasks.

Schema details

Install type: cli
Troubleshooting: No

Source repository stats

Scope: Source repo

Collection metadata

Estimated setup: 5 minutes
Difficulty: advanced

Full copyable content

{
  "mcpServers": {
    "iterm-mcp": {
      "command": "npx",
      "args": ["-y", "iterm-mcp"]
    }
  }
}

About this resource

Content

iTerm MCP is a local Model Context Protocol server that connects Claude to the active iTerm2 terminal session. It lets the model write text into the terminal, read a requested number of output lines, and send control characters such as Control-C or Escape.

The server is designed for supervised local terminal assistance, REPL workflows, and CLI sessions where the user wants to watch what Claude is doing. It is not a sandbox and does not include command safety restrictions.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm registry metadata, package metadata, source implementation, terminal executor, output reader, control-character sender, and license for current installation steps, tool behavior, terminal control details, and safety notes.

Features

npm package iterm-mcp.
Stdio MCP server launched with npx -y iterm-mcp.
write_to_terminal tool for writing text to the active iTerm2 session.
read_terminal_output tool for reading a requested number of terminal output lines.
send_control_character tool for sending terminal control characters.
AppleScript integration through osascript.
Active iTerm2 session and TTY detection.
Support for REPL and interactive CLI workflows.
MIT license.

Installation

Configure an MCP client on macOS with iTerm2 running:

{
  "mcpServers": {
    "iterm-mcp": {
      "command": "npx",
      "args": ["-y", "iterm-mcp"]
    }
  }
}

Before using the server, select the intended iTerm2 tab and keep the terminal visible. Start with small, reversible commands until the workflow is trusted.

Use Cases

Ask Claude to inspect the last few lines of a long-running command.
Let Claude help inside a supervised REPL session.
Run small CLI commands while watching the active terminal.
Send Control-C to interrupt a command after human approval.
Debug command output without copying terminal text into chat manually.
Pair with a developer who wants model help in the same shell session they are watching.

Safety and Privacy

iTerm MCP is effectively local terminal control. It can type commands into the active shell, interact with REPLs, interrupt processes, and read terminal scrollback. Use it only when you can supervise the active tab and stop the model if it goes off course.

Avoid using it in privileged shells, production SSH sessions, terminals with secrets in scrollback, or workspaces where accidental commands could damage data. Review commands before execution, and keep destructive operations outside model control unless a human explicitly approves the exact action.

Duplicate Check

Existing content mentions iTerm2 incidentally in a terminal setup guide, but no iTerm MCP, ferrislucas/iterm-mcp, iterm-mcp, or matching source URL entry was found in content/mcp.

#terminal#iterm2#shell#local-mcp#developer-tools