Nps vs Git
A side-by-side look at the Nps and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nps for environment & nature work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nps when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_NPS_KEY. - You want tools like
list_parks, get_park, list_alerts.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Version Control |
| Quality signal | 59/100 · Good | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | PLATFORM_NPS_KEY | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,512 |
| Directory activity | 1 views 0 installs 0 upvotes | 49 views 0 installs 0 upvotes |
| Tools | 6 | 16 |
| Full listing | View Nps | View Git |
Tools & capabilities
Nps tools 6
list_parksList or search NPS parks. Filter by free-text query, state code (2-letter, comma-separated), or parkCode list. Returns full name, description, designation, states, GPS, address, official URL.get_parkFetch a single park by parkCode. Returns full description, designation, activities, topics, address, contacts, operating hours, entrance fees, and image gallery.list_alertsCurrent park alerts — closures, road conditions, weather warnings, danger advisories. Filter by parkCode or state.list_campgroundsCampgrounds inside a park or state. Returns name, description, RV/tent capacity, amenities, reservation info, GPS.list_things_to_doActivities recommended by the park service — hikes, ranger programs, scenic drives, ranger-led activities. Filter by parkCode or state.nps_visitationNational park visitor statistics — how many people visited a park. Answers "how many people visited Yellowstone", "NPS visitation numbers", "annual visitors to Grand Canyon", "busiest national park", "park attendance by month". Monthly + annual recreation and total visitor counts from the NPS Visitor Use Statistics service (keyless). Pass a park name or 4-letter code (e.g., YELL, GRCA, GRSM) and a year, or system_total:true for the whole national park system. Example: {"park":"yellowstone","year":2023}.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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.
Nps
{
"mcpServers": {
"nps": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nps"
],
"env": {
"PLATFORM_NPS_KEY": "YOUR_PLATFORM_NPS_KEY_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Nps is categorized under Environment & Nature and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Nps for environment & nature work and Git for version control.
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.
Nps has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. 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 nps and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nps has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars.