Labsco
MCP SERVER

MCP Server for National Park Services Data

by amysatterlee ↗

Ask which national parks are in a state and get details on any of them, straight from the National Park Service API.

Geospatial & Mapping Data
Summary
Two tools, and the prompts do the translating.

The useful design choice is shipping prompts alongside the tools: park codes like `yell` are not something anyone remembers, so the prompt layer takes a plain question — what parks are in CA, tell me about Yellowstone — and turns it into the right call. Free data, free key, nothing to keep running.

What it is

A small MCP server over the National Park Service API with two tools and two matching prompts: list the parks in a US state, and fetch the detail for one park by its NPS code.

What you get
  • `park-list` — takes a two-letter `stateCode` and returns the parks there, each with full name, description and park code
  • `park-details` — takes a `parkCode` and returns that park's detail, including which states it spans
  • Two prompts that wrap the tools in the questions people actually ask: `parks-by-state` and `details-for-park`
Requirements

A National Park Service API key, free from the NPS developer page, supplied as `API_KEY`. Node.js v18 or newer with npm or yarn; installation is a clone plus `npm install` and `npm run build`, then pointing the client at `build/index.js`. The package is `nps` (1.0.0 in package.json).

Setup effort

One command plus a key — npx -y nps, then supply credentials