Connections & Capabilities
Connects To
Capabilities
Quickstart
Install
npx -y @smithery/cli install @KyrieTangSheng/mcp-server-nationalparks --client claudeConfig
{
"mcpServers": {
"nationalparks": {
"command": "npx",
"args": ["-y", "mcp-server-nationalparks"],
"env": {
"NPS_API_KEY": "YOUR_NPS_API_KEY"
}
}
}
}Exposed MCP Tools (6)
findParksSearches for national parks based on criteria like state, name, or activities.
Read-only operation; no modification of data.
getParkDetailsRetrieves detailed information about a specific national park.
Read-only operation; no modification of data.
getAlertsRetrieves current alerts for national parks, including closures and hazards.
Read-only operation; no modification of data.
getVisitorCentersRetrieves information about visitor centers in national parks.
Read-only operation; no modification of data.
getCampgroundsRetrieves information about campgrounds in national parks.
Read-only operation; no modification of data.
getEventsFinds upcoming events at national parks.
Read-only operation; no modification of data.
Safety Assessment
This server is relatively safe due to its read-only nature and reliance on the NPS API. However, the security of the NPS API key is paramount. Ensure the API key is stored securely and consider implementing rate limiting and input validation to mitigate potential risks.
- Primarily read-only operations.
- No direct filesystem access.
- Rate limits imposed by the NPS API provide some protection against abuse.
- No user authentication required beyond the API key.
- Requires an NPS API key, which needs to be securely stored.
- Potential for information disclosure if API key is compromised.
- External API dependency introduces a point of failure.
- Input sanitization relies on the server implementation.
