Iterm MCP vs Remote Agents
A side-by-side look at the Iterm MCP and Remote Agents MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Iterm MCP for command line work as a local process; choose Remote Agents 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?
Choose 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.
Choose Remote Agents when
- You need dedicated capabilities in the Command Line domain.
- You prefer a local stdio subprocess transport.
- You want tools like
exec, read_file, get_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Command Line | Command Line |
| Quality signal | 65/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 570 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 15 |
| Full listing | View Iterm MCP | View Remote Agents |
Tools & capabilities
Iterm MCP tools 3
write_to_terminalWrites text to the active iTerm terminal - often used to run a command in the terminalread_terminal_outputReads the output from the active iTerm terminalsend_control_characterSends a control character to the active iTerm terminal (e.g., Control-C, or special sequences like ']' for telnet escape)
Remote Agents tools 15
execRun a shell command (locally or on a remote agent via `agent_id`)read_fileFile operations (write requires Edit/Bypass)get_infoInspect / change an agent's mode at runtimegit_statusGit operationsschedule_addCron-style tasks on a hosttask_dispatchAutonomous AI tasks run with the host's own credentialssession_listBrowse the host's AI-chat history (claude / opencode / codex / cline / roo / kilo / zed / cursor / gemini / qwen / goose / continue); `session_get` fetches a transcript or a window around one messagesession_searchFull-text search over the host's AI-chat history — a local Tantivy (BM25) index of every provider transcript, returning ranked cited snippets with `session_id` + message position (follow up with `session_get { around_seq }` for the context)list_agentsList agents connected to the relay roomfleet_execRun an operation across the fleet — `target = all \fleet_session_searchSearch the AI-chat history across the whole fleet: every matched host queries its local index, hits merge by score with host labelsfile_searchFind files on a host, and move a file host→host (UDP, SHA-256 verified)- +3 more on 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": {
"ferrislucas-iterm-mcp": {
"command": "npx",
"args": [
"-y",
"iterm-mcp"
]
}
}
}
Remote Agents
{
"mcpServers": {
"remote-agents": {
"command": "npx",
"args": [
"-y",
"remote-agents"
]
}
}
}
Frequently asked questions
Iterm MCP is categorized under Command Line and uses a local stdio subprocess. Remote Agents belongs to Command Line and uses a local stdio subprocess. Pick Iterm MCP for command line work and Remote Agents 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.
Iterm MCP is listed as free. Auth: no auth required. Remote Agents 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 remote-agents 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. Remote Agents has 56/100 (Good) with 1 views, 0 installs and 1 GitHub stars.