What iterminal MCP server does
The iterminal MCP server lets an AI assistant work with SSH connections configured in iTerminal. Its documented MCP scope covers three main areas: running commands on connected servers, performing remote file operations, and reading system-monitoring data.
The surrounding iTerminal application is designed for developers, operations engineers, and DevOps teams managing multiple servers. It provides connection records, multi-session terminals, terminal splits, SFTP browsing, file transfers, and monitoring for CPU, memory, disks, and processes. The MCP layer makes selected SSH operations available to an assistant while the application displays AI-initiated activity in the terminal.
Use the iterminal MCP server when the target hosts are already managed through iTerminal and an assistant needs operational access through those connections. The repository does not describe the MCP layer as a general-purpose local shell server or as a replacement for iTerminal's connection manager.
How it works
The application includes an MCP implementation under its mcp source directory. According to the project documentation, the server communicates over HTTP with SSE transport and protects access with a token. An AI client connects to that endpoint, then uses MCP tools to control SSH sessions held by iTerminal.
The SSH implementation is part of the Tauri desktop application and uses Rust libraries for SSH and SFTP. This means the MCP interface operates in the context of iTerminal's configured connections, including password or SSH-key authentication.
The host application stores connection information with AES-256-GCM encryption and supports OpenSSH and PEM key formats. However, host-key verification is currently skipped according to the security notes, so deployments should account for that behavior before using the server with sensitive infrastructure.
Setup and configuration
The repository documents building iTerminal rather than a separate MCP package installation. The development prerequisites are Node.js 18 or newer, Rust 1.75 or newer, and npm or pnpm. Platform-specific dependencies include Visual Studio Build Tools and WebView2 on Windows, Xcode Command Line Tools on macOS, and several GTK/WebKit-related packages on Ubuntu or Debian.
A development checkout can be installed with the project's package manager and started with the Tauri development command. Production artifacts are created with the Tauri build command and are placed under src-tauri/target/release/bundle/. The resulting formats include MSI or EXE for Windows, DMG or APP for macOS, and DEB or AppImage for Linux.
The README confirms token authentication and SSE transport for the embedded MCP server but does not provide configuration names or startup instructions for exposing it.
Tools and capabilities
The documented MCP capabilities include:
- Execute commands through SSH connections.
- Perform remote file operations.
- Read system-monitoring information.
The broader desktop application also supports SFTP uploads and downloads, file creation, deletion, renaming, permission changes, archive operations, search, preview, and editing. It includes monitoring for host information, CPU, memory, disks, and processes, plus process termination.
Limitations and notes
The iterminal MCP server depends on iTerminal's configured SSH connections and the desktop application.
Host-key verification is reported as disabled, with known_hosts support planned for a later version. The application also has no automatic session lock, so unused connections should be disconnected manually. Authentication supports passwords and SSH keys, but the project recommends key-based authentication in its security notes.
Treat those as desktop features unless the server's tool definitions confirm otherwise.