What is the key difference between Next Devtools MCP and Wickworks?

Next Devtools MCP belongs to the Cloud Platforms category with local stdio execution, while Wickworks belongs to the Cloud Platforms category with local stdio execution.

How do I install Next Devtools MCP or Wickworks in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Next Devtools MCP and Wickworks free or paid?

Next Devtools MCP operates under a Free / Open Source model (No auth required). Wickworks operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Next Devtools MCP lists 4 tools with 5 views and 818 GitHub stars. Wickworks lists 0 tools with 0 views and 1 GitHub stars.

Can I use both Next Devtools MCP and Wickworks together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Next Devtools MCP vs Wickworks

In-depth architectural comparison of the Next Devtools MCP and Wickworks 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: 86/100 (Excellent) | Auth: No auth required

Wickworks

Cloud Platforms · Local stdio

Quality: 29/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Next Devtools MCP if you need specialized Cloud Platforms tools running via a local process. Choose Wickworks if your workspace requires Cloud Platforms integration with local subprocess execution. 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).
Primary tools included: nextjs_index, nextjs_call, nextjs_docs.

Explore Next Devtools MCP Details

Choose Wickworks 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).

Explore Wickworks Details

Feature & Specification Comparison

Specification	Next Devtools MCP vercel VerifiedCloud Platforms	Wickworks Cloud Platforms
Summary	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.	Self-hosted MCP server: technical indicators + smart-money-concepts from OHLC bars.
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.

Wickworks Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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 Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "add-mcp"
      ]
    }
  }
}

Wickworks Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wickworks": {
      "command": "npx",
      "args": [
        "-y",
        "wickworks"
      ]
    }
  }
}

Frequently Asked Questions

Next Devtools MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Wickworks belongs to Cloud Platforms using local stdio subprocess. Select Next Devtools MCP when you need capabilities focused on cloud platforms and Wickworks when you require tools for cloud platforms.

More alternatives to Next Devtools MCP More alternatives to Wickworks Cloud Platforms category hub