# Nps [Health: Active]

**Category:** 🌳 Environment & Nature  
**Repository:** https://github.com/pipeworx-io/mcp-nps  
**GitHub Stars:** 0  
**npm Downloads (last month):** 448  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nps

## Description
NPS MCP — US National Park Service (free key, generous limits)

## Tools
Capabilities this server exposes over MCP:

- **list_parks** — List 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_park** — Fetch a single park by parkCode. Returns full description, designation, activities, topics, address, contacts, operating hours, entrance fees, and image gallery.
- **list_alerts** — Current park alerts — closures, road conditions, weather warnings, danger advisories. Filter by parkCode or state.
- **list_campgrounds** — Campgrounds inside a park or state. Returns name, description, RV/tent capacity, amenities, reservation info, GPS.
- **list_things_to_do** — Activities recommended by the park service — hikes, ranger programs, scenic drives, ranger-led activities. Filter by parkCode or state.
- **nps_visitation** — National 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}.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "nps": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-nps"],
    "env": {
      "PLATFORM_NPS_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_NPS_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/nps/readme_