MCP Server for National Park Services Data

Created By
amysatterleea year ago
Model Context Protocol (MCP) Server for National Park Services data
Overview

what is MCP Server for National Park Services Data?

The MCP Server provides an interface to retrieve data from the National Park Services (NPS), allowing users to access information about national parks across the United States.

how to use MCP Server?

To use the MCP Server, clone the repository, install the necessary dependencies, set up your NPS API key in a .env file, and run the server using Node.js.

key features of MCP Server?

  • Retrieve a list of national parks by state.
  • Fetch detailed information about specific national parks.
  • Utilizes the National Park Service API for data retrieval.

use cases of MCP Server?

  1. Finding national parks in a specific U.S. state.
  2. Obtaining detailed descriptions and information about individual national parks.
  3. Integrating national park data into applications or services.

FAQ from MCP Server?

  • Do I need an API key to use the MCP Server?

Yes, a valid NPS API key is required to access the data.

  • What technologies are required to run the MCP Server?

You need Node.js (v18+ recommended) and npm or yarn to run the server.

  • Can I run the MCP Server on any operating system?

Yes, as long as you have Node.js installed, you can run it on any OS.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
amysatterlee
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago