park-listLABSCO 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-letterstateCodeand returns the parks there, each with full name, description and park codepark-details— takes aparkCodeand returns that park's detail, including which states it spans- Two prompts that wrap the tools in the questions people actually ask:
parks-by-stateanddetails-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
Build from source — git clone https://github.com/amysatterlee/nps_mcp.git
USE CASES
01
Planning a trip through a state
List every national park in that state with a short description of each, then dig into the ones worth the detour.
02
Looking up one park by name
Ask about it in plain language and let the prompt resolve it to the park code before fetching the detail.
03
Finding parks that span state lines
Read the states field on a park's detail record to see everywhere it reaches.
2 tools
Listed in project docs. Your client may show a different list.
park-detailsBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation. Tool names use hyphens: park-list and park-details.
Requires
- Node.js
- API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/amysatterlee/nps_mcp.git
cd nps_mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"nps": {
"command": "node",
"args": [
"<YOUR_PATH_TO_NPS_MCP>/build/index.js"
],
"env": {
"API_KEY": "<YOUR_API_KEY>"
}
}
}
}
