MCP Server Nationalparks vs Nws
A side-by-side look at the MCP Server Nationalparks and Nws MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Nationalparks for environment & nature work as a local process; choose Nws for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Nationalparks when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NPS_API_KEY. - You want tools like
stateCode, q, limit.
Choose Nws when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 59/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | NPS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 41 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View MCP Server Nationalparks | View Nws |
Tools & capabilities
MCP Server Nationalparks tools 8
stateCodeqlimitstartactivitiesparkCodedateStartdateEnd
Nws tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Nationalparks
{
"mcpServers": {
"kyrietangsheng-mcp-server-nationalparks": {
"command": "npx",
"args": [
"-y",
"mcp-server-nationalparks"
],
"env": {
"NPS_API_KEY": "YOUR_NPS_API_KEY_HERE"
}
}
}
}
Nws
{
"mcpServers": {
"nws": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nws"
]
}
}
}
Frequently asked questions
MCP Server Nationalparks is categorized under Environment & Nature and uses a local stdio subprocess. Nws belongs to Environment & Nature and uses a local stdio subprocess. Pick MCP Server Nationalparks for environment & nature work and Nws for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server Nationalparks is listed as free. Auth: api key required. Nws has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kyrietangsheng-mcp-server-nationalparks and nws as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Nationalparks has a quality signal of 59/100 (Good) with 4 views, 0 installs and 41 GitHub stars. Nws has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.
