National Parks MCP Server
Related Servers
Alternatives to National Parks MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides access to the National Park Service API to search for U.S. national parks, view park details, check alerts and closures, find visitor centers, campgrounds, and upcoming events.90 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides access to the National Park Service API, enabling natural language queries about parks, alerts, campgrounds, events, and more.MIT
- AlicenseNot gradedqualityDmaintenanceFacilitates retrieval of National Park Services data using the NPS API, allowing users to list national parks by state and access detailed information about specific parks.28,449 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides LLM context on U.S. national parks by integrating National Park Service, Recreation.gov, and weather APIs, enabling queries about park info, trails, alerts, events, weather forecasts, and more via tool calls.3MIT

@pipeworx/npsofficial
AlicenseNot gradedqualityBmaintenanceEnables natural-language access to US National Park Service data, including parks, alerts, campgrounds, and things-to-do, via MCP tools or the ask_pipeworx routing feature.3 npmMIT- AlicenseNot gradedqualityAmaintenancePlan US National Park Service trips — find parks, check alerts and closures, find campgrounds, browse things to do and events via the NPS Data API. Supports STDIO and Streamable HTTP.424 npm2Apache 2.0
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting different aspects of national park information: searching parks, getting alerts, campgrounds, events, park details, and visitor centers. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming follows a consistent verb_noun pattern with 'get' or 'find' prefixes (e.g., getAlerts, findParks), but there is a minor deviation with 'findParks' using 'find' instead of 'get', and all tools use camelCase consistently. This slight inconsistency is minor and does not hinder readability.
With 6 tools, the server is well-scoped for providing national park information. Each tool serves a distinct and useful purpose, covering key areas like search, alerts, amenities, events, details, and visitor centers without being overly broad or sparse.
The tool set covers most core aspects of national park information, including search, alerts, amenities, events, details, and visitor centers. A minor gap might be the lack of tools for booking or reservation-related operations, but the existing tools support comprehensive querying and information retrieval for the domain.