MCP server
by rishabkoul
iTerm2 lets you interact with macOS terminals using AI, AppleScript, and Node.js for seamless command execution and outp
Enables AI assistants to directly control iTerm2 terminals on macOS, executing commands and reading output without switching contexts.
iTerm2 is a community-built MCP server published by rishabkoul that provides AI assistants with tools and capabilities via the Model Context Protocol. iTerm2 lets you interact with macOS terminals using AI, AppleScript, and Node.js for seamless command execution and outp It is categorized under developer tools. This server exposes 5 tools that AI clients can invoke during conversations and coding sessions.
You can install iTerm2 in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
ISC
iTerm2 is released under the ISC license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We evaluated iTerm2 against two servers with overlapping tools; this profile had the clearer scope statement.
iTerm2 is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
iTerm2 has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend iTerm2 for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: iTerm2 surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, iTerm2 benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend iTerm2 for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
iTerm2 has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, iTerm2 benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: iTerm2 surfaces stars and publisher context so we could sanity-check maintenance before adopting.
showing 1-10 of 31
A Model Context Protocol (MCP) server implementation for iTerm2 terminal integration. This server allows AI assistants to interact with iTerm2 terminals through the Model Context Protocol.
The server uses the standard MCP configuration options. No additional configuration is required.
To use this server with Cursor, add the following configuration to your ~/.cursor/mcp.json file:
{
"mcpServers": {
"terminal": {
"command": "npx",
"args": ["iterm_mcp_server"]
}
}
}
open_terminal: Open a new terminal instanceexecute_command: Execute a command in a specific terminalread_output: Read the output from a specific terminalclose_terminal: Close a specific terminallist_terminals: List all active terminals and their informationContributions are welcome! Please feel free to submit a Pull Request.
ISC
Rishab Koul
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.