Git vs Nws
A side-by-side look at the Git 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 Git for version control 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 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.
Choose Nws when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_forecast, get_hourly_forecast, get_alerts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Environment & Nature |
| Quality signal | 81/100 · Excellent | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | 0 |
| Directory activity | 49 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 16 | 5 |
| Full listing | View Git | View Nws |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Nws tools 5
get_forecastGet the 7-day NWS forecast for a US lat/lon. Returns named periods (e.g., "Tonight", "Wednesday") with high/low temperature, wind, and a short text forecast. US locations only.get_hourly_forecastGet the hourly NWS forecast for a US lat/lon (~168 hours). Useful for short-term planning, severe-weather windows, or precipitation timing.get_alertsActive NWS watches / warnings / advisories. Filter by US state (2-letter code), point (lat,lon), severity, or status. Returns event name, severity, urgency, headline, description, affected areas, and effective/expires times.get_observationLatest observation from a specific NWS weather station. Returns temperature, humidity, wind, visibility, pressure, and present-weather codes.get_stationsFind NWS weather observation stations in a US state (e.g., "CA", "NY", "TX"). Returns station IDs (use with get_observation), names, time zones, and coordinates. US only.
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.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Nws
{
"mcpServers": {
"nws": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-nws"
]
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Nws belongs to Environment & Nature and uses a local stdio subprocess. Pick Git for version control 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.
Git is listed as free. Auth: no auth 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 git and nws as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars. Nws has 57/100 (Good) with 3 views, 0 installs and 0 GitHub stars.