Netlogger MCP vs Next Devtools MCP
A side-by-side look at the Netlogger 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.
N
Netlogger MCPDeveloper Tools · Local subprocess (stdio)NetLogger MCP server. Nets on the air, live check-ins and who's up, past nets.53GoodAuth: no auth requiredVerdict: choose Netlogger MCP 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.
Which MCP server should you choose?
NChoose Netlogger 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 have the keys it needs:
NETLOGGER_MCP_CALLSIGN, NETLOGGER_MCP_MOCK. - You want tools like
netlogger_active_nets, netlogger_checkins, netlogger_past_nets.
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 | N Netlogger MCP | |
|---|---|---|
| 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 | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | NETLOGGER_MCP_CALLSIGNNETLOGGER_MCP_MOCK | 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 | 6 | 4 |
| Full listing | View Netlogger MCP | View Next Devtools MCP |
Tools & capabilities
Netlogger MCP tools 6
netlogger_active_netsNets on the air now: frequency, band, mode, net control, logger, monitoring countnetlogger_checkinsA live net's check-in list, plus the pointer (the station being worked now)netlogger_past_netsClosed nets over the last N days, with the net IDs past check-ins neednetlogger_past_checkinsA closed net's check-in listnetlogger_set_callsignSave your callsign (asked once, on first use)get_version_infoService version + upstream spec version (fleet identity attestation)
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.
Netlogger MCP
{
"mcpServers": {
"netlogger-mcp": {
"command": "uvx",
"args": [
"netlogger-mcp"
],
"env": {
"NETLOGGER_MCP_CALLSIGN": "YOUR_NETLOGGER_MCP_CALLSIGN_HERE",
"NETLOGGER_MCP_MOCK": "YOUR_NETLOGGER_MCP_MOCK_HERE"
}
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Netlogger MCP is categorized under Developer Tools and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Netlogger MCP for developer tools 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.
Netlogger 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 netlogger-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, Netlogger MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 8 views, 0 installs and 828 GitHub stars.