Next Devtools MCP vs Watson Orchestrate

A side-by-side look at the Next Devtools MCP and Watson Orchestrate MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Next Devtools MCP logoNext 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 requiredWatson Orchestrate logoWatson OrchestrateDeveloper Tools · Local subprocess (stdio)Manage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude.49FairAuth: not declared

Verdict: choose Next Devtools MCP for developer tools work as a local process; choose Watson Orchestrate 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?

Next Devtools MCP logoChoose 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.
Explore Next Devtools MCP

Watson Orchestrate logoChoose Watson Orchestrate when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: WO_API_KEY, WO_INSTANCE_URL.
  • You want tools like list_skills, list_tools_with_connections, list_standard_tools.
Explore Watson Orchestrate

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNext Devtools MCP logoNext Devtools MCPWatson Orchestrate logoWatson Orchestrate
CategoryDeveloper ToolsDeveloper Tools
Quality signal86/100 · Excellent49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedWO_API_KEYWO_INSTANCE_URL
Verified owner VerifiedCommunity listing
GitHub stars8320
Directory activity 9 views 0 installs 1 upvotes 0 views 0 installs 0 upvotes
Tools423

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.

Watson Orchestrate tools 23

  • list_skills
  • list_tools_with_connections
  • list_standard_tools
  • get_skill
  • delete_skill
  • deploy_skill
  • deploy_tool_from_url
  • create_python_tool_from_tool_spec_json
  • tool-spec.json
  • python_code
  • requirements
  • create_python_tool_and_upload
  • +11 more on 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Watson Orchestrate

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "watson-orchestrate": {
      "command": "npx",
      "args": [
        "-y",
        "wxo-builder-mcp-server"
      ],
      "env": {
        "WO_API_KEY": "YOUR_WO_API_KEY_HERE",
        "WO_INSTANCE_URL": "YOUR_WO_INSTANCE_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Watson Orchestrate belongs to Developer Tools and uses a local stdio subprocess. Pick Next Devtools MCP for developer tools work and Watson Orchestrate 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.

Next Devtools MCP is listed as free. Auth: no auth required. Watson Orchestrate has no declared pricing — check the project's own site. 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 watson-orchestrate 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 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars. Watson Orchestrate has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.