Nps vs Next Devtools MCP

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

Nps logoNpsEnvironment & Nature · Local subprocess (stdio)NPS MCP — US National Park Service (free key, generous limits)59GoodAuth: 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 Nps for environment & nature 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?

Nps logoChoose Nps when

  • You need dedicated capabilities in the Environment & Nature domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PLATFORM_NPS_KEY.
  • You want tools like list_parks, get_park, list_alerts.
Explore Nps

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.

SpecNps logoNpsNext Devtools MCP logoNext Devtools MCP
CategoryEnvironment & NatureDeveloper Tools
Quality signal59/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsPLATFORM_NPS_KEYNone listed
Verified ownerCommunity listing Verified
GitHub stars0832
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools64

Tools & capabilities

Nps tools 6

  • list_parksList or search NPS parks. Filter by free-text query, state code (2-letter, comma-separated), or parkCode list. Returns full name, description, designation, states, GPS, address, official URL.
  • get_parkFetch a single park by parkCode. Returns full description, designation, activities, topics, address, contacts, operating hours, entrance fees, and image gallery.
  • list_alertsCurrent park alerts — closures, road conditions, weather warnings, danger advisories. Filter by parkCode or state.
  • list_campgroundsCampgrounds inside a park or state. Returns name, description, RV/tent capacity, amenities, reservation info, GPS.
  • list_things_to_doActivities recommended by the park service — hikes, ranger programs, scenic drives, ranger-led activities. Filter by parkCode or state.
  • nps_visitationNational park visitor statistics — how many people visited a park. Answers "how many people visited Yellowstone", "NPS visitation numbers", "annual visitors to Grand Canyon", "busiest national park", "park attendance by month". Monthly + annual recreation and total visitor counts from the NPS Visitor Use Statistics service (keyless). Pass a park name or 4-letter code (e.g., YELL, GRCA, GRSM) and a year, or system_total:true for the whole national park system. Example: {"park":"yellowstone","year":2023}.

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.

Nps

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

Next Devtools MCP

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

Frequently asked questions

Nps is categorized under Environment & Nature and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Nps for environment & nature 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.

Nps 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 nps and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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