SmartCLI drive Tui vs Iterm MCP
A side-by-side look at the SmartCLI drive Tui and Iterm MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose SmartCLI drive Tui for command line work as a local process; 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?
Choose SmartCLI drive Tui when
- You need dedicated capabilities in the Command Line domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Command Line | Command Line |
| Quality signal | 41/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 570 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View SmartCLI drive Tui | View Iterm MCP |
Tools & capabilities
SmartCLI drive Tui 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 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)
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.
SmartCLI drive Tui
{
"mcpServers": {
"smartcli-drive-tui": {
"command": "uvx",
"args": [
"--from",
"smartcli-toolkit",
"smartcli-mcp"
]
}
}
}
Iterm MCP
{
"mcpServers": {
"ferrislucas-iterm-mcp": {
"command": "npx",
"args": [
"-y",
"iterm-mcp"
]
}
}
}
Frequently asked questions
SmartCLI drive Tui is categorized under Command Line and uses a local stdio subprocess. Iterm MCP belongs to Command Line and uses a local stdio subprocess. Pick SmartCLI drive Tui 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.
SmartCLI drive Tui 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 smartcli-drive-tui and ferrislucas-iterm-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SmartCLI drive Tui has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 5 GitHub stars. Iterm MCP has 65/100 (Great) with 4 views, 0 installs and 570 GitHub stars.