NPS Park Alerts & Conditions
Pricing
Pay per usage
NPS Park Alerts & Conditions
Scrape current alerts, closures, and conditions for US National Park Service sites. Filter by state and category. No API key required.
NPS Park Alerts & Conditions
Pricing
Pay per usage
Scrape current alerts, closures, and conditions for US National Park Service sites. Filter by state and category. No API key required.
Connect the NPS Park Alerts & Closures — US National Park Service Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrupulous_waterbird_m4w/nps-park-alerts" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the NPS Park Alerts & Closures — US National Park Service Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the NPS Park Alerts & Closures — US National Park Service Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,scrupulous_waterbird_m4w/nps-park-alerts.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.