A side-by-side look at the RoamProxy 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 RoamProxy for developer tools 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.
ROAM_API_TOKEN.fetch_url, get_proxy, check_ip.nextjs_index, nextjs_call, nextjs_docs.Rows where the two servers differ are marked.
| Spec | R RoamProxy | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | ROAM_API_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 828 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 1 upvotes |
| Tools | 4 | 4 |
| Full listing | View RoamProxy | View Next Devtools MCP |
fetch_urlFetch a URL through a proxy IP in the chosen country / state / city. Returns status + body as markdown, text or HTML.get_proxyBuild a ready-to-use `http://` or `socks5://` proxy URL (plus Playwright config) for any geo, rotating or sticky.check_ipShow the exit IP, city, region and ISP for a geo/session, to verify targeting.account_statusWallet balance, per-GB prices, last 7 days of usage, rented static IPs.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.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.
{
"mcpServers": {
"roamproxy": {
"command": "npx",
"args": [
"-y",
"roamproxy-mcp"
],
"env": {
"ROAM_API_TOKEN": "YOUR_ROAM_API_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}