Skip to main content
Glama
aviation-weather-mcp

aviation-weather-mcp

by mariow

Aviation Weather MCP Server

Aviation weather briefings directly in Claude. METARs, TAFs, PIREPs, SIGMETs, and ICON-D2 NWP forecasts — no API key required.

Just ask Claude things like:

  • "METAR EDDM"

  • "Preflight briefing EDLI"

  • "Route weather EDDM to LOWI"

  • "Any SIGMETs over Germany?"

Prerequisites

You need two things installed:

  1. Claude Desktop — download from https://claude.ai/download

  2. Node.js — download from https://nodejs.org (pick the LTS version). Use a patched release: 22.23.4+, 24.22.1+, or 26.12.1+. These carry the October 2026 security fixes (including a Brotli-decoder RCE reachable through fetch); older builds and the end-of-life Node 20 are vulnerable. The server prints a warning on startup if it detects an unpatched Node.

To check if Node.js is already installed, open Terminal (Mac) or Command Prompt (Windows) and type:

node --version

If you see a version at or above v22.23.4 (or v24.22.1 / v26.12.1), you're good to go. If it's lower, update Node from https://nodejs.org.

Related MCP server: SimBrief Flight Planning MCP Server

Setup (3 minutes)

Step 1: Open the Claude Desktop config

  1. Open Claude Desktop

  2. Click the gear icon (top right) to open Settings

  3. Go to Developer

  4. Click Edit Config

This opens a JSON file in your text editor.

Step 2: Add the weather server

If the file is empty or just has {}, replace it with:

{
  "mcpServers": {
    "aviation-weather": {
      "command": "npx",
      "args": ["-y", "aviation-weather-mcp"]
    }
  }
}

If the file already has content (e.g. other MCP servers), add the "aviation-weather" block inside the existing "mcpServers" section.

Step 3: Restart Claude Desktop

Quit Claude Desktop completely and reopen it. The first start may take 10-15 seconds longer while it downloads the weather server.

Step 4: Test it

Start a new chat and ask: "METAR EDDF"

Claude should respond with the current weather at Frankfurt airport. If it works, you're all set!

What can it do?

Ask Claude...

What it does

"METAR EDDM"

Current weather at Munich airport

"TAF EDDF"

Forecast for Frankfurt

"Preflight briefing EDLI"

Full VFR brief: METAR + TAF + NWP forecast

"Route weather EDDM to LOWI"

Weather along a direct route (METARs + NWP + SIGMETs)

"Outlook for EDFE next week"

Per-day VFR go/no-go probability for the next 3–15 days

"Any PIREPs near EDDK?"

Recent pilot reports near Cologne

"SIGMETs over Germany"

Active significant weather warnings

"Hourly forecast for 48.14, 11.57"

ICON-D2 NWP model data for any coordinates

Data Sources

  • aviationweather.gov — METARs, TAFs, PIREPs, SIGMETs (FAA/NOAA, worldwide)

  • Open-Meteo — ICON-D2 / ICON-EU NWP forecasts (DWD models)

  • Open-Meteo Ensemble — ensemble forecasts (ECMWF-ENS, GEFS) for the long-range outlook

  • OurAirports — bundled offline ICAO → coordinates database (~22k airports, incl. GA fields), Public Domain

Notes

  • Works worldwide for METARs, TAFs, PIREPs, and SIGMETs

  • ICON-D2 high-resolution forecasts (2km) cover Central Europe (43-58°N / 4-21°E, 48h horizon)

  • Outside Central Europe, it falls back to ICON-EU (7km resolution, 120h horizon)

  • ICAO codes are resolved automatically — just use the 4-letter code. Resolution works offline from a bundled airport database, so even pure GA fields without a METAR (e.g. EDVY) work; you can also pass lat/lon directly

  • Visibility is reported in km

  • Open-Meteo serves no usable cloud base, so the hourly NWP forecasts (wx_icon_d2, wx_preflight, wx_route) derive a cloud ceiling from pressure-level cloud cover (lowest broken/overcast deck ≥50%, in ft AGL). The output always states it explicitly — ceil ~1700ft, ceil none<8600ft (no deck below), or ceil n/a (no data) — so a missing ceiling never looks like clear skies

  • The 3–15 day outlook is a coarse confidence measure (share of ensemble members with poor VFR conditions), not a precise forecast. It uses low-cloud cover as the VFR proxy (Open-Meteo serves no usable cloud base) and shows the ECMWF-IFS trend plus an ICON-EU cross-check for the first ~5 days

Usage with Claude Code

claude mcp add aviation-weather -- npx -y aviation-weather-mcp

Troubleshooting

Claude doesn't show weather tools: Make sure you restarted Claude Desktop after editing the config. Check that the JSON syntax is valid (no trailing commas, matching brackets).

"npx: command not found": Node.js is not installed or not in your PATH. Download it from https://nodejs.org.

Slow first start: The first time, npx downloads the package (~30KB). After that it's cached and starts instantly.

Disclaimer

This tool is for informational purposes only and is not a replacement for an official pre-flight weather briefing. Always use approved weather services and follow your national aviation authority's requirements for flight preparation.

License

MIT

Available Tools

8 tools
wx_icon_d2A

Get DWD ICON-D2 NWP forecast for any lat/lon. Provides hourly wind (10m + 80m), visibility, cloud base, precipitation, and CAPE. ICON-D2 covers Central Europe at 2km resolution up to 48h. Falls back to ICON-EU (7km, Europe) or ICON-seamless outside coverage.

Inputs: lat (required), lon (required), hours.

wx_metarA

Get the latest METAR for an airport. Returns raw METAR plus decoded ceiling, visibility, wind, and VFR/MVFR/IFR/LIFR flight category.

Inputs: icao (required).

wx_outlookA

Longer-range VFR confidence outlook (3–15 days) for an airfield or location. Pools an ensemble (ECMWF-ENS for low cloud; ECMWF-ENS + GEFS for CAPE) and reports, per day, the probability that the day is NO-GO — the share of ensemble members with poor VFR conditions (low cloud above threshold OR high CAPE/thunderstorm potential) during the daylight window. Also shows the deterministic ECMWF-IFS trend, plus the ICON-EU run (≤5 days) as an independent medium-range cross-check that sits between ICON-D2 (48h) and ECMWF (15d). This is the confidence measure for trip planning that short-range METAR/TAF/ICON-D2 cannot provide. Pass an ICAO code (resolved offline from a bundled airport database covering GA fields) or lat/lon directly.

Inputs: lat, lon, days, icao, +4 more.

wx_pirepsA

Get pilot reports (PIREPs) near an airport. Reports recent turbulence, icing, cloud tops, and other in-flight observations.

Inputs: icao (required), radius_nm.

wx_preflightA

VFR preflight weather brief for an airfield. Combines current METAR, TAF, and ICON-D2 NWP forecast into a single assessment. Only the ICAO code is required — coordinates are resolved authoritatively from the aviationweather.gov station database. Never supply coordinates yourself.

Inputs: icao (required), hours.

wx_routeA

Route weather brief for a direct flight between two airports. Fetches METARs at departure and destination, ICON-D2 at 5 points along the great-circle route, and active SIGMETs. Coordinates are resolved from the station API — never guess them. Pass ICAO codes exactly as given by the user.

Inputs: to_icao (required), from_icao (required), hours_enroute, forecast_horizon.

wx_sigmetsB

Get active SIGMETs and AIRMETs. Filter by region to reduce noise.

Inputs: region.

wx_tafA

Get the Terminal Area Forecast (TAF) for an airport. Returns raw TAF plus decoded forecast periods with flight category, wind, visibility, and ceiling.

Inputs: icao (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct weather product or composite: METAR, TAF, PIREPs, SIGMETs, high-res model, long-range outlook, preflight brief, and route brief. No two tools serve the same purpose; even the combined briefs (preflight/route) are clearly differentiated from single-source tools.

    Naming Consistency5/5

    All tools share the 'wx_' prefix followed by a lowercase, underscore-separated product identifier (metar, taf, pireps, sigmets, icon_d2, outlook, preflight, route). The convention is uniform and predictable, making tool selection straightforward.

    Tool Count5/5

    Eight tools form a well-scoped set for an aviation weather server. Each tool covers a distinct data source or derived product without redundancy, and the count is neither too thin nor overwhelming.

    Completeness5/5

    The surface covers the full range of standard aviation weather products (current observations, forecasts, warnings, PIREPs, model data) plus composite briefings for preflight and route planning. No critical workflow is missing; all dependent data sources are also available as standalone tools.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      D
      quality
      D
      maintenance
      Provides real-time weather forecasts and alerts by fetching data from the National Weather Service API, allowing Claude to answer weather-related questions with up-to-date information.
      2
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to official aviation weather data including METARs, TAFs, and PIREPs directly from aviationweather.gov. It enables users to query airport observations, forecasts, and pilot reports through natural language within Claude.
      -