What is the main functional difference between Harvis.dev and Next Devtools MCP?

Harvis.dev is categorized under Developer Tools and uses an install path we have not confirmed yet. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Harvis.dev for developer tools work and Next Devtools MCP for developer tools.

How do I install Harvis.dev or Next Devtools MCP in Claude Desktop, Cursor, or Windsurf?

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. Harvis.dev has no confirmed install command yet — follow its own setup instructions.

Are Harvis.dev and Next Devtools MCP free to use, or do they require API keys?

Harvis.dev has no declared pricing — check the project's own site. 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.

Can I run both Harvis.dev and Next Devtools MCP at the same time in my AI client?

Yes. MCP clients support multiple servers: add harvis-dev and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Harvis.dev has a quality signal of 37/100 (Fair) 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.

Harvis.dev vs Next Devtools MCP

A side-by-side look at the Harvis.dev 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.

Harvis.devDeveloper ToolsDeploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.37FairAuth: not declared

Next Devtools MCPDeveloper Tools · Local subprocess (stdio)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.86ExcellentAuth: no auth required

Verdict: choose Harvis.dev for developer tools work; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Spec	H Harvis.dev	Next Devtools MCP
Category	Developer Tools	Developer Tools
Quality signal	37/100 · Fair	86/100 · Excellent
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Verified
GitHub stars	—	828
Directory activity	0 views 0 installs 0 upvotes	8 views 0 installs 1 upvotes
Tools	Not listed	4
Full listing	View Harvis.dev	View Next Devtools MCP

Harvis.dev vs Next Devtools MCP

Which MCP server should you choose?

H
Choose Harvis.dev when

Choose Next Devtools MCP when

Feature & specification comparison

Tools & capabilities

Harvis.dev tools

Next Devtools MCP tools 4

Ready-to-paste client configs

Harvis.dev

Next Devtools MCP

Frequently asked questions

HChoose Harvis.dev when