Next Devtools MCP vs Zenodo

A side-by-side look at the Next Devtools MCP and Zenodo 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 requiredZenodo logoZenodoResearch · Local subprocess (stdio)Zenodo (CERN) open research data repository57GoodAuth: not declared

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

Zenodo logoChoose Zenodo when

  • You need dedicated capabilities in the Research domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search, record, record_files.
Explore Zenodo

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNext Devtools MCP logoNext Devtools MCPZenodo logoZenodo
CategoryDeveloper ToolsResearch
Quality signal86/100 · Excellent57/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars8320
Directory activity 9 views 0 installs 1 upvotes 3 views 0 installs 0 upvotes
Tools45

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.

Zenodo tools 5

  • searchSearch Zenodo open-research repository for datasets, publications, software, and other research outputs by keyword query. Filterable by type, community, and sort order (mostrecent/bestmatch/mostviewed); returns metadata, DOI, and file links.
  • recordSingle record by Zenodo id.
  • record_filesList files attached to a Zenodo record by its numeric id. Returns file names, sizes, checksums, and direct download URLs.
  • communitiesList or search Zenodo communities (thematic collections of records) by optional keyword query; returns community id, title, description, and record count.
  • community_recordsFetch paginated records belonging to a Zenodo community by its slug id (e.g. "openaire"). Returns record metadata, DOIs, and file links for all items in the community.

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"
      ]
    }
  }
}

Zenodo

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "zenodo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-zenodo"
      ]
    }
  }
}

Frequently asked questions

Next Devtools MCP is categorized under Developer Tools and uses a local stdio subprocess. Zenodo belongs to Research and uses a local stdio subprocess. Pick Next Devtools MCP for developer tools work and Zenodo for research.

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. Zenodo 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 zenodo 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. Zenodo has 57/100 (Good) with 3 views, 0 installs and 0 GitHub stars.