Shell Use vs Iterm MCP

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

Shell Use logoShell UseCommand LineLet agents use the shell like a human.25EmergingAuth: not declaredIterm 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 required

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

Which MCP server should you choose?

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecShell Use logoShell UseIterm MCP logoIterm MCP
CategoryCommand LineCommand Line
Quality signal25/100 · Emerging65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsSHELL_USE_SESSIONSSHELL_USE_SOCKETNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0570
Directory activity 2 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Shell Use tools

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

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)

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.

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.

Iterm MCP

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

Frequently asked questions

Shell Use is categorized under Command Line and uses an install path we have not confirmed yet. Iterm MCP belongs to Command Line and uses a local stdio subprocess. Pick Shell Use for command line work and Iterm MCP 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.

Shell Use has no declared pricing — check the project's own site. Iterm MCP is listed as free. Auth: no auth required. 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 shell-use and ferrislucas-iterm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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