Next Devtools MCP vs Wati
A side-by-side look at the Next Devtools MCP and Wati MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WatiDeveloper ToolsManage Wati contacts, conversations, campaigns, templates and Astra AI agents.35FairAuth: oauth 2.0Verdict: choose Next Devtools MCP for developer tools work as a local process; choose Wati for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
WChoose Wati when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wati | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 82/100 · Excellent | 35/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
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.
Wati tools
No tool names declared yet. Check the project README from 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.
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Wati
No confirmed install command for Wati yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Wati belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Next Devtools MCP for developer tools work and Wati 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. Wati has no confirmed install command yet — follow its own setup instructions.
Next Devtools MCP is listed as free. Auth: no auth required. Wati is listed as free. Auth: oauth 2.0. 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 vercel-next-devtools-mcp and wati as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Next Devtools MCP has a quality signal of 82/100 (Excellent) with 7 views, 0 installs and 825 GitHub stars. Wati has 35/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.