Iterm MCP vs Next Devtools MCP
A side-by-side look at the Iterm MCP and Next Devtools MCP 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 Next Devtools MCP for developer tools 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 Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Command Line | Developer Tools |
| Quality signal | 65/100 · Great | 86/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 | 832 |
| Directory activity | 4 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 3 | 4 |
| Full listing | View Iterm MCP | View Next Devtools MCP |
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)
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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"
]
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Iterm MCP is categorized under Command Line and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Iterm MCP for command line work and Next Devtools MCP for developer tools.
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. Next Devtools 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 ferrislucas-iterm-mcp and vercel-next-devtools-mcp 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. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.
