Summary
Trip questions answered from the park service's records rather than a travel blog.
The six tools share one shape — a parkCode plus q, limit and start for paging — so once findParks returns the code the rest is mechanical. Everything reads: nothing here reserves a campsite or registers you for an event. getEvents is the only tool that takes a date window, so alerts, hours and amenities are whatever the park service is publishing at the moment you call.
What it is
A read-only server over National Park Service data, keyed throughout by the parkCode that findParks returns.
What you get
- Park search by state code, activity, or free text, returning the parkCode every other tool takes
- One park's full record through getParkDetails
- Current alerts — closures, hazards and notices — for a named park or across parks
- Visitor centres with their operating hours
- Campgrounds with their amenities
- Upcoming events, narrowed by a dateStart and dateEnd window
Requirements
An NPS API key in NPS_API_KEY.
Setup effort
One command plus a key — npx -y @smithery/cli install @KyrieTangSheng/mcp-server-nationalparks --client claude, then supply credentials