Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@iTerm MCP Server run 'npm install' in a new terminal window"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Create and manage iTerm2 terminal sessions
Execute commands in terminals
Read terminal output
List active terminals
Close terminals
Related MCP server: MCP Terminal
Node.js >= 14.x
iTerm2
macOS (since iTerm2 is macOS-only)
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 instance
execute_command: Execute a command in a specific terminal
read_output: Read the output from a specific terminal
close_terminal: Close a specific terminal
list_terminals: List all active terminals and their information
The server validates all input using Zod schemas
Commands are executed in isolated terminal sessions
Proper error handling and input sanitization is implemented
Contributions are welcome! Please feel free to submit a Pull Request.
ISC
Rishab Koul
Close a specific terminal
Inputs: terminalId (required).
Execute a command in a specific terminal
Inputs: terminalId (required), command (required).
List all active terminals and their information
Inputs: no named parameters.
Open a new terminal instance
Inputs: no named parameters.
Read the output from a specific terminal
Inputs: terminalId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: list-terminals enumerates terminals, open-terminal creates new ones, close-terminal removes them, execute-command runs commands, and read-output retrieves output. An agent can easily differentiate these functions without confusion.
All tools follow a consistent verb-noun pattern with hyphen separation (e.g., list-terminals, open-terminal, execute-command). The naming is uniform, predictable, and readable throughout the set.
With 5 tools, this server is well-scoped for terminal management. Each tool earns its place by covering essential operations: listing, opening, closing, executing commands, and reading output, which is appropriate for the domain.
The tool set provides complete lifecycle coverage for terminal management: create (open-terminal), read (list-terminals, read-output), update (execute-command), and delete (close-terminal). There are no obvious gaps, and agents can perform all core workflows without dead ends.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to control Unreal E…
