NPS Explorer MCP Server 🔭
About
A Model Context Protocol (MCP) server on Cloudflare Workers, letting you query APIs for park overviews, trails, alerts, events, weather forecasts, and more via simple tool calls from your LLM of choice.
Details
- Author
- Kyle-Ski
- GitHub stars
- 3
- Downloads
- 160
- Categories
- Other, AI
Jump to
- Query comprehensive park information and current conditions
- Find parks by state, activities, or amenities
- Retrieve current alerts, closures, and notifications
- Get upcoming park events (ranger talks, guided hikes, etc.)
- Plan visits with historical and forecast weather recommendations
- List campgrounds with detailed information
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
NPS Explorer MCP Server 🔭Command (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Clone the repository, copy .dev.vars.example to .dev.vars and populate it with your own API keys. Then install dependencies with npm i and run locally with npm start. Deploy to Cloudflare Workers with npm run deploy. Test connectivity using the MCP Server Inspector (npx @modelcontextprotocol/inspector).
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"nps explorer mcp server \ud83d\udd2d": {
"nps-explorer-mcp-server": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector"
]
}
}
}
}
McpServers
{
"nps-explorer-mcp-server": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector"
]
}
}
NPS Explorer MCP Server 🔭
Overview
This repository is a modified version of Cloudflare’s remote-MCP-GitHub-OAuth demo, extended into a National Parks Service Explorer. It provides an LLM context on U.S. national parks by integrating:
- The National Park Service API
- The Recreation.gov API
- A Weather API (I chose https://www.weatherapi.com/)
It runs as a Model Context Protocol (MCP) server on Cloudflare Workers, letting you query park overviews, trails, alerts, events, weather forecasts, and more via simple tool calls to the LLM.
> Looking for the original demo?
> See Cloudflare’s instructions here.
>
> Want to add this tool directly to your Claude Desktop?
> Checkout the instructions here
>
> Want to clone their example directly? Use their command line to get a server going on your machine:
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-github-oauth
---
📋 Prerequisites
- A Cloudflare account with Workers and KV enabled
- Node.js v18.20.4+ and npm
- Your own API keys for:
- National Park Service API
- Recreation.gov API
- Weather API (weatherapi)
---
⚙️ Setup
1. Clone this repo
git clone https://github.com/Kyle-Ski/nps-explorer-mcp-server.git
cd nps-explorer-mcp-server
2. Copy and fill .dev.vars
cp .dev.vars.example .dev.vars
_Then open .dev.vars and populate with your own secrets._
NPS API
rec.gov API
Weather API (or whatever you choose)
Create a GitHub OAuth App
3. Install dependencies
npm i
4. Run Locally
npm start
---
🚀 Deployment
Thedeploy command is using Wrangler to deploy your server to Cloudflare Workers! Cloudflare will also use their Durable Objects and Workers KV.
npm run deploy
---
🧰 Tools
| Tool Name | Description | Status |
|--------------------------|---------------------------------------------------------------------------------------------------|--------------------|
| getParkInfo | Get comprehensive information about a national park including both static details and current conditions | working |
| getTrailInfo | Get detailed information about trails (difficulty, length, elevation gain, current conditions) | 🚧 under construction |
| findParks | Find national parks based on criteria such as state, activities, or amenities | working |
| getParkAlerts | Get current alerts, closures, and notifications for specified parks | working |
| getParkEvents | Get upcoming events at parks including ranger talks, guided hikes, and educational programs | working |
| findNearbyRecreation | Find recreation areas and camping options near a given location | ⚠️ not working correctly |
| planParkVisit | Get recommendations for the best time to visit a park based on historical and forecast weather | working |
| getParkWeatherForecast | Get detailed weather forecast for a national park by park code | working |
| getCampgrounds | List campgrounds within a given national park with detailed information | working |
---
🧪 Testing
Once your server is up and running, use the MCP Server Inspector Tool to make sure your server can connect and show you the tools and resources it has access to.npx @modelcontextprotocol/inspector
---
🛜 For Production
_All of this is in the original Cloudflare README.md_ Cloudflare recommends creating a local and remote GitHub OAuth App: For the Homepage URL, specifyhttps://mcp-github-oauth.<your-subdomain>.workers.dev
For the Authorization callback URL, specify https://mcp-github-oauth.<your-subdomain>.workers.dev/callback
Note your Client ID and generate a Client secret and add them via Wrangler.
wrangler secret put GITHUB_CLIENT_ID
wrangler secret put GITHUB_CLIENT_SECRET
wrangler secret put COOKIE_ENCRYPTION_KEY # add any random string here e.g. openssl rand -hex 32
Set up a KV namespace
Create the KV namespace: wrangler kv:namespace create "OAUTH_KV"
Update the Wrangler file with the KV ID
---
📚 Reference
Original Cloudflare Demo README: https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-github-oauth#readme Model Context Protocol: https://modelcontextprotocol.io/introduction Connecting an agent to your server:---
🧑🔧 Troubleshooting and Common Issues
_Check out the MCP troubleshooting docs_Connecting to Claude Desktop Fails:
- Most commonly due to Node incompatibility issues, use node v18.20.4+ locally and checkout this guide I wrote.
---
🤝 Contributing
1. Fork this repository2. Create a feature branch (git checkout -b feature-name)
3. Commit your changes (git commit -m 'Add new tool')
4. Push to the branch (git push origin feature-name)
5. Open a Pull Request
⚖️ License
his project is licensed under the MIT License. See LICENSE for details.Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.




