In-depth architectural comparison of the Next Devtools MCP and Hatchable MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Next Devtools MCP
Cloud Platforms · Local stdio
Quality: 87/100 (Excellent) | Auth: No auth required
Hatchable MCP
Cloud Platforms · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Next Devtools MCP if you need specialized Cloud Platforms tools running via a local process. Choose Hatchable MCP if your workspace requires Cloud Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Next Devtools MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.
Build and host full-stack web apps and sites on Hatchable from any MCP client. DB, auth, storage, domains, and cron per project. Free tier.
Category & Scope
Tools & Capabilities Breakdown
Next Devtools MCP Tools (4)
nextjs_index
Discover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_call
Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docs
Gateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_eval
Gateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Hatchable MCP Tools (6)
Project creation, listing, updating, forking, and visibility controls
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Next Devtools MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Hatchable MCP belongs to Cloud Platforms using remote streaming HTTP/SSE transport. Select Next Devtools MCP when you need capabilities focused on cloud platforms and Hatchable MCP when you require tools for cloud platforms.