I14y MCP vs Next Devtools MCP

A side-by-side look at the I14y MCP 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.

I14y MCP logoI14y MCPDeveloper Tools · Local subprocess (stdio)MCP server for I14Y — Switzerland's national open-data metadata catalogue (DCAT-AP-CH)52GoodAuth: not declaredNext 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 required

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

I14y MCP logoChoose I14y MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_catalog, list_datasets, get_dataset.
Explore I14y MCP

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecI14y MCP logoI14y MCPNext Devtools MCP logoNext Devtools MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal52/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars0832
Directory activity 0 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools134

Tools & capabilities

I14y MCP tools 13

  • search_catalogFree-text search across the catalogue. Entry point.
  • list_datasetsPaginated dataset register (complete, unlike search).
  • get_datasetFull metadata record for one dataset.
  • get_dataset_distributionsDownload URLs, formats and **licences**.
  • list_data_servicesRegister of official Swiss APIs with endpoint URLs.
  • get_data_serviceFull record for one registered interface.
  • list_public_servicesAdministrative services for citizens.
  • list_conceptsHarmonised concepts and code lists.
  • get_conceptOne concept definition.
  • search_codelist_entriesIndividual codes of a code list.
  • list_publishersPublishing bodies, with Swiss UID.
  • list_catalogsContributing catalogues.
  • +1 more on the listing page

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.

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.

I14y MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "i14y-mcp": {
      "command": "uvx",
      "args": [
        "i14y-mcp"
      ]
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

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

I14y MCP 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.

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

On AllMCPs, I14y MCP has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.