Met No vs Open Meteo

In-depth architectural comparison of the Met No and Open Meteo 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?

Choose Met No when:

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

Explore Met No Details

Choose Open Meteo when:

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

Explore Open Meteo Details

Feature & Specification Comparison

Specification	Met No Environment & Nature	Open Meteo Environment & Nature
Summary	MET Norway weather (api.met.no behind yr.no) — global forecast, sunrise, ocean	Open-Meteo MCP — weather forecast + historical reanalysis + sister APIs
Category & Scope	Environment & Nature	Environment & Nature
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": {
    "met-no": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-met-no"
      ]
    }
  }
}

{
  "mcpServers": {
    "open-meteo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-open-meteo"
      ]
    }
  }
}

Related MCP Server Comparisons