National Parks MCP Server

An MCP server that provides programmatic access to the U.S. National Park Service (NPS) API. It fetches real-time data about parks, alerts, visitor centers, campgrounds, and events.

For details on connecting to and using MCP servers, see the official documentation at mcp.apify.com.

Key Features

The server exposes six main tools for querying NPS data:

• findParks: Search for parks by state, activity, name, or description. Supports pagination.
• getParkDetails: Retrieve comprehensive details for a specific park using its park code (e.g., yose for Yosemite).
• getAlerts: Check for current alerts, closures, and hazards, filterable by park.
• getVisitorCenters: Get locations, hours, and contact info for park visitor centers.
• getCampgrounds: Find campgrounds, including amenities, fees, and reservation details.
• getEvents: Discover upcoming events, filterable by date range and park.

All list-based tools (findParks, getAlerts, getVisitorCenters, getCampgrounds, getEvents) support common optional parameters for control:
* limit: Max results to return (default 10, max 50).
* start: Start position for pagination.
* q: A search term to filter by title or description.
* parkCode: Filter by a specific park code or comma-separated list of codes.

How to Use

Interact with the server by calling its tools with specific parameters. The core interaction pattern is requesting data filtered by criteria like park code, state, or date.

Example Queries:

• Find parks in a state: Use findParks with a stateCode (e.g., "CO").
• Get park details: Use getParkDetails with a parkCode (e.g., "yell" for Yellowstone).
• Check for closures: Use getAlerts with a parkCode to see active alerts.
• Find campgrounds: Use getCampgrounds with a parkCode and optional q for amenities.
• Look up events: Use getEvents with parkCode, dateStart, and dateEnd parameters.

Input/Output

Inputs:
Tools accept specific string or number parameters. Common optional inputs include:
* parkCode: A string identifier for a park (e.g., "grca").
* stateCode: A two-letter U.S. state code (e.g., "CA"). For multiple states, use a comma-separated string ("CA,OR,WA").
* dateStart / dateEnd: Dates in YYYY-MM-DD format for event filtering.
* activities: A comma-separated string like "hiking,camping" to filter parks.

Outputs:
Returns structured JSON data from the NPS API. For example:
* findParks returns an array of matching parks with basic info.
* getParkDetails returns a detailed object containing descriptions, operating hours, fees, and contact information for the specified park.