Log inSubmit server
Nps logo

Nps

Access National Park Service parks, alerts, campgrounds, and activities through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nps

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "nps": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-nps"
      ],
      "env": {
        "PLATFORM_NPS_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Nps MCP server exposes US National Park Service data through tools for finding parks, reading park details, and browsing alerts, campgrounds, and activities. It can run as a local stdio package or through the Pipeworx gateway over MCP and HTTP. Gateway access supports a platform key or a user-supplied NPS API key, while the standalone package avoids the gateway. Reach for it when an agent needs current NPS location or trip-planning data.

Use cases

  • Search parks by state or text query
  • Retrieve details for a known park code
  • Check current park alerts
  • Find campgrounds near a park
  • Browse National Park Service activities

Key features

  • Park search with filters and pagination
  • Park lookup by park code
  • Alert, campground, and activity listings
  • Hosted MCP and HTTP access
  • Standalone stdio execution
  • Optional gateway-wide question routing

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-nps (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads448Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Nps works

What Nps MCP server does

Nps MCP server connects MCP-compatible agents with the US National Park Service API at https://developer.nps.gov/api/v1/. Its tools cover five practical data tasks: searching parks, retrieving one park by code, and listing alerts, campgrounds, or things to do. Filters such as state, park code, and text query are available on the relevant list operations.

The package is intended for questions and workflows involving National Park Service data. For example, an agent can search for parks in a state, retrieve details for a known park code, or find campground and activity records associated with a park.

How it works

Nps MCP server is available in two forms. The hosted option is a scoped endpoint at https://gateway.pipeworx.io/nps/mcp. It lists the NPS tools along with shared Pipeworx meta-tools. Those gateway tools can route broader questions across the Pipeworx catalog, which contains more data sources than the NPS pack alone.

The local option runs @pipeworx/mcp-nps through stdin and stdout. It responds to MCP initialize, tools/list, and tools/call operations, and exposes only the NPS pack tools. Both forms use the same underlying NPS source.

Without an MCP client, the gateway also provides HTTP tool endpoints. For example, POST https://gateway.pipeworx.io/v1/tools/list_parks accepts a JSON request, while a GET request to the same tool path can be used to inspect it.

Setup and configuration

For a hosted connection, add the NPS gateway URL to an MCP client configuration. Claude Desktop, Cursor, and Windsurf are named as supported client options in the project instructions. A full Pipeworx gateway URL is also available when an agent should list every pack directly rather than only the NPS tools.

Authentication can use the gateway platform variable PLATFORM_NPS_KEY. Alternatively, requests can provide an NPS developer key as the _apiKey query parameter. The key is obtained by registering with the National Park Service developer portal.

For a local setup, configure the client to run npx -y @pipeworx/mcp-nps, or execute that command to verify that the process starts. The standalone mode does not require a Pipeworx account.

Tools and capabilities

The Nps MCP server provides these tools:

  • list_parks: searches parks with optional query, state, park-code, limit, and start parameters.
  • get_park: retrieves a park using its park code.
  • list_alerts: lists alerts with optional park, state, query, and limit filters.
  • list_campgrounds: lists campgrounds with optional park, state, query, and limit filters.
  • list_things_to_do: lists activities with optional park, state, query, and limit filters.

The gateway additionally includes shared tools such as ask_pipeworx, discover_tools, search_within, remember, and recall. These are gateway features rather than part of the standalone NPS process.

Limitations and notes

The hosted pack endpoint always includes the shared gateway meta-tools; they cannot currently be removed from that connection. Its exact tool scope may change, so the initialize response is the authoritative source for the active connection. Use the standalone package when only the NPS tools are needed without gateway routing, or use the full gateway when direct access to all catalog packs is preferred.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nps

Nps is an MCP server that connects AI agents to the US National Park Service API for park listings, park details, alerts, campgrounds, and things-to-do data. Its main tools are list_parks, get_park, list_alerts, list_campgrounds, and list_things_to_do, with filtering and pagination options where supported.

Run `npx -y @pipeworx/mcp-nps` for the standalone server, or add that command and package to an MCP client configuration. You can instead connect the client to `https://gateway.pipeworx.io/nps/mcp` for the hosted gateway version.

Yes, Nps works with Cursor through the hosted MCP URL. Add `https://gateway.pipeworx.io/nps/mcp` as the server URL in the client configuration.

The hosted gateway can use `PLATFORM_NPS_KEY`, or requests can supply an NPS developer key through the `_apiKey` query parameter.

Related MCP servers

All in Environment & Nature All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNps AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nps?style=directory)](https://allmcps.com/mcp/nps)
HTML Embed
<a href="https://allmcps.com/mcp/nps"><img src="https://allmcps.com/api/badge/nps?style=directory" alt="Nps on AllMCPs" /></a>