Iterm MCP vs Filesystem
A side-by-side look at the Iterm MCP and Filesystem 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 Filesystem for file systems 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 Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Command Line | File Systems |
| Quality signal | 65/100 · Great | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 570 | 91,512 |
| Directory activity | 4 views 0 installs 0 upvotes | 10 views 0 installs 0 upvotes |
| Tools | 3 | 17 |
| Full listing | View Iterm MCP | View Filesystem |
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)
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 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"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Iterm MCP is categorized under Command Line and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Iterm MCP for command line work and Filesystem for file systems.
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. Filesystem 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 ferrislucas-iterm-mcp and filesystem 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. Filesystem has 85/100 (Excellent) with 10 views, 0 installs and 91,512 GitHub stars.