NPS Explorer MCP Server - MCP Server

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

Clone this repo

git clone https://github.com/Kyle-Ski/nps-explorer-mcp-server.git
cd nps-explorer-mcp-server

Copy and fill .dev.vars
```
cp .dev.vars.example .dev.vars
```
Then open .dev.vars and populate with your own secrets.

Install dependencies

npm i

Run Locally

npm start

🚀 Deployment

The deploy 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, specify https://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

Fork this repository
Create a feature branch (git checkout -b feature-name)
Commit your changes (git commit -m 'Add new tool')
Push to the branch (git push origin feature-name)
Open a Pull Request

⚖️ License

his project is licensed under the MIT License. See LICENSE for details.