What is the key difference between Meteostat and Nws?

Meteostat belongs to the Developer Tools category with cloud HTTP/SSE execution, while Nws belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Meteostat or Nws in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Meteostat and Nws free or paid?

Meteostat operates under a Free / Open Source model (No auth required). Nws operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Meteostat lists 0 tools with 0 views and 0 GitHub stars. Nws lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Meteostat and Nws together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Meteostat vs Nws

In-depth architectural comparison of the Meteostat and Nws MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Meteostat

Developer Tools · Remote HTTP/SSE

Quality: 35/100 (Fair) | Auth: No auth required

Nws

Developer Tools · Remote HTTP/SSE

Quality: 37/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Meteostat if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Nws if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Meteostat when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Meteostat Details

Choose Nws when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Nws Details

Feature & Specification Comparison

Specification	Meteostat Developer Tools	N Nws Developer Tools
Summary	Meteostat MCP — historical weather from 11k+ stations (no auth)	NWS MCP — US National Weather Service (no auth)
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Meteostat Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Nws Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Meteostat Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "meteostat": {
      "url": "https://pipeworx.io"
    }
  }
}

Nws Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "nws": {
      "url": "https://pipeworx.io"
    }
  }
}

Frequently Asked Questions

Meteostat is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Nws belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Meteostat when you need capabilities focused on developer tools and Nws when you require tools for developer tools.

More alternatives to Meteostat More alternatives to Nws Developer Tools category hub