Iterm MCP vs Shell Use

A side-by-side look at the Iterm MCP and Shell Use MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Iterm MCP logoIterm MCPCommand Line · Local subprocess (stdio)A Model Context Protocol server that provides access to iTerm. You can run commands and ask questions about what you see in the iTerm terminal.65GreatAuth: no auth requiredShell Use logoShell UseCommand LineLet agents use the shell like a human.25EmergingAuth: not declared

Verdict: choose Iterm MCP for command line work as a local process; choose Shell Use for command line. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Iterm MCP logoChoose Iterm MCP when

  • You need dedicated capabilities in the Command Line domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like write_to_terminal, read_terminal_output, send_control_character.
Explore Iterm MCP

Shell Use logoChoose Shell Use when

  • You need dedicated capabilities in the Command Line domain.
  • You have the keys it needs: SHELL_USE_SESSIONS, SHELL_USE_SOCKET.
Explore Shell Use

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIterm MCP logoIterm MCPShell Use logoShell Use
CategoryCommand LineCommand Line
Quality signal65/100 · Great25/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedSHELL_USE_SESSIONSSHELL_USE_SOCKET
Verified ownerCommunity listingCommunity listing
GitHub stars5700
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools3Not listed

Tools & capabilities

Iterm MCP tools 3

  • write_to_terminalWrites text to the active iTerm terminal - often used to run a command in the terminal
  • read_terminal_outputReads the output from the active iTerm terminal
  • send_control_characterSends a control character to the active iTerm terminal (e.g., Control-C, or special sequences like ']' for telnet escape)

Shell Use tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Iterm MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ferrislucas-iterm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "iterm-mcp"
      ]
    }
  }
}

Shell Use

No confirmed install command for Shell Use yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Iterm MCP is categorized under Command Line and uses a local stdio subprocess. Shell Use belongs to Command Line and uses an install path we have not confirmed yet. Pick Iterm MCP for command line work and Shell Use for command line.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Shell Use has no confirmed install command yet — follow its own setup instructions.

Iterm MCP is listed as free. Auth: no auth required. Shell Use has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ferrislucas-iterm-mcp and shell-use as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Iterm MCP has a quality signal of 65/100 (Great) with 4 views, 0 installs and 570 GitHub stars. Shell Use has 25/100 (Emerging) with 2 views, 0 installs and 0 GitHub stars.