Iterm MCP Server

A Model Context Protocol server that provides access to the currently active tab of iTerm

Local serverstdio

What is the Iterm MCP MCP server?

Iterm mcp mcp server lets Claude, Cursor and other MCP clients work with Iterm MCP directly. A Model Context Protocol server that provides access to the currently active tab of iTerm.

What Iterm MCP does

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Tools it exposes

Once connected, the assistant can call these 7 tools directly:

  • write_to_terminal — Writes to the active iTerm terminal, often used to run a command. Returns the number of lines of output produced by the command
  • read_terminal_output — Reads the requested number of lines from the active iTerm terminal
  • send_control_character — Sends a control character to the active iTerm terminal
  • Features — The Features tool exposed by this server
  • Tools — The Tools tool exposed by this server
  • Requirements — The Requirements tool exposed by this server
  • Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Installing the iterm mcp mcp server

The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Requirements

  • iTerm2 must be running * Node version 18 or greater

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Iterm MCP sits in that group, and the shape of its toolset — write_to_terminal, read_terminal_output, send_control_character among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • With 7 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Iterm MCP.
  • Maintained by lite.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the iterm mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
write_to_terminalWrites to the active iTerm terminal, often used to run a command. Returns the number of lines of output produced by the command.
read_terminal_outputReads the requested number of lines from the active iTerm terminal.
send_control_characterSends a control character to the active iTerm terminal.
FeaturesThe Features tool exposed by this server.
ToolsThe Tools tool exposed by this server.
RequirementsThe Requirements tool exposed by this server.
DebuggingSince MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

How to install the Iterm MCP MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

  • iTerm2 must be running * Node version 18 or greater

Example prompts to try

  • Use Iterm MCP to write to terminal.
  • Use Iterm MCP to read terminal output.
  • Use Iterm MCP to send control character.

Frequently asked questions

It connects Iterm MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (write_to_terminal, read_terminal_output, send_control_character, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Iterm MCP directly.