Weathersight vs Meteoswiss MCP

In-depth architectural comparison of the Weathersight and Meteoswiss MCP 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.

Which MCP Server Should You Choose?

W

Choose Weathersight when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Weathersight Details

Choose Meteoswiss MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Meteoswiss MCP Details

Feature & Specification Comparison

Specification	W Weathersight Developer Tools	Meteoswiss MCP Developer Tools
Summary	Historical weather and climate: 100+ years of station data, normals, extremes, and trends.	MeteoSwiss Open Data for weather, climate normals, warnings
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "weathersight": {
      "command": "npx",
      "args": [
        "-y",
        "weathersight"
      ]
    }
  }
}

{
  "mcpServers": {
    "meteoswiss-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

Related MCP Server Comparisons