Nps MCP Server

Nps mcp mcp server lets Claude, Cursor and other MCP clients work with Nps MCP directly. MCP using National Park Service API.

What Nps MCP does

This MCP Server provides an interface to retrieve National Park Services (NPS) data. It allows users to: - Retrieve a list of national parks in a given U.S. state. - Fetch detailed information about a specific national park.

Installing the nps mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js (v18+ recommended) - npm or yarn - A valid NPS API key (available at https://www.nps.gov/subjects/developer/get-started.htm) - Claude Desktop installed (for running MCP servers)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Nps MCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by amysatterlee.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the nps mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.