Log inSubmit server
Aviation Weather MCP Server logo

Aviation Weather MCP Server

Fetch and structure NWS aviation observations, forecasts, pilot reports, and domestic SIGMETs through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Aviation Weather MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aviation-weather-mcp-server": {
      "command": "bunx",
      "args": [
        "@cyanheads/aviation-weather-mcp-server@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

bunx @cyanheads/aviation-weather-mcp-server@latest

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 8d ago.

Overview

NWS Aviation Weather Center data reaches agents through the aviation-weather-mcp-server MCP server, including METARs, TAFs, PIREPs, and domestic SIGMETs. Five tools resolve stations, retrieve weather reports, and return decoded fields alongside source text; one prompt structures a preflight briefing. It runs over STDIO, local Streamable HTTP, or the listed public hosted endpoint. Reach for it when an agent needs station-specific or regional aviation weather from the NWS source.

Use cases

  • Build a preflight weather briefing
  • Check METARs and flight categories near an airport
  • Compare TAF periods for selected airports
  • Search PIREPs along a region or altitude band
  • Find active domestic SIGMETs in an area

Key features

  • NWS Aviation Weather Center data access
  • Decoded METAR and TAF fields with raw reports
  • Station lookup by identifier, state, or bounding box
  • PIREP searches with altitude and intensity filters
  • Domestic SIGMETs with hazard polygons
  • Preflight briefing prompt

Tools5

What Aviation Weather MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~310 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 18h ago via OSV.dev · @cyanheads/aviation-weather-mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads1.3kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed5Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Aviation Weather MCP Server works

What aviation-weather-mcp-server does

The aviation-weather-mcp-server MCP server exposes NWS Aviation Weather Center data to MCP clients. It covers current airport observations, terminal forecasts, recent pilot reports, and active domestic SIGMETs. Results include decoded weather fields and the original report text, giving an agent both structured values for reasoning and source strings for reference.

The server provides five tools and one prompt. aviation_find_stations resolves station identifiers or searches by geographic bounding box and US state. aviation_get_metar retrieves current observations, aviation_get_taf returns forecast periods, aviation_get_pireps searches recent pilot reports, and aviation_get_advisories returns active domestic SIGMETs. The aviation_preflight_brief prompt sequences these tools into a flight-weather briefing.

How it works

Station discovery accepts identifiers, bounding boxes, or two-letter state codes. Identifier lookups use the registry's station IDs, such as four-character ICAO values; returned records can also include IATA and FAA aliases. Search results include coordinates, elevation, supported data types, and information about result limits.

METAR requests can target named stations or survey an area. Station requests return observations within a configurable one-to-twelve-hour window, while area searches return the latest observation for each reporting station. Results can be narrowed by flight category, such as IFR or LIFR. METAR output includes wind, visibility, ceiling, weather, temperature, dew point, altimeter, cloud layers, flight category, observation type, and the raw string.

TAF results contain ISO 8601 validity times, change types and probabilities, decoded weather groups, cloud layers, vertical visibility, and low-level wind shear where reported. PIREP searches use either a station and radius or a bounding box, with optional altitude and turbulence or icing intensity filters. Advisory results include hazard type, severity, altitude range, validity, polygon coordinates, and raw text.

Setup and configuration

The aviation-weather-mcp-server MCP server supports three connection styles: a STDIO process, a local Streamable HTTP server, and the public hosted endpoint at https://aviation-weather.caseyjhand.com/mcp. The README provides installation links for Claude Desktop, Cursor, and VS Code. It also identifies an npm package and a Docker container image, so deployment can use the package or the published container according to the chosen connection mode.

Tools and capabilities

  • Resolve stations by identifier, state, or geographic bounds.
  • Retrieve METAR observations with decoded flight categories and cloud information.
  • Retrieve TAF periods with forecast changes, probabilities, and wind shear.
  • Search PIREPs by location, distance, area, altitude, turbulence, or icing intensity.
  • Retrieve active domestic SIGMETs with hazard geometry and validity details.
  • Generate a structured preflight briefing with the included prompt.

Limitations and notes

Station identifier lookup does not resolve three-letter IATA codes directly; use the station's four-character registry identifier or discover it first. Several operations have per-call bounds, including up to 20 station IDs for discovery, 10 stations for METAR requests, and four stations for TAF requests.

Area searches can encounter the upstream 400-row cap. The tools report when that cap affects a result and expose limits or time-window controls where applicable. A wider METAR time window can use the cap on repeated observations instead of additional stations. Missing requested stations are reported rather than silently omitted.

The data scope is the NWS Aviation Weather Center, and the advisory tool is documented for active domestic SIGMETs. The server does not claim to provide general worldwide aviation weather coverage.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aviation Weather MCP Server

aviation-weather-mcp-server is an MCP server that connects AI clients to the NWS Aviation Weather Center. Its main tools find stations, retrieve METARs and TAFs, search PIREPs, and fetch active domestic SIGMETs. It also includes a preflight briefing prompt and supports STDIO or Streamable HTTP connections.

Install it through the provided Claude Desktop, Cursor, or VS Code links, or use its npm package with an MCP client. The server also supports a Docker image, local STDIO or Streamable HTTP operation, and a public hosted endpoint.

Yes, aviation-weather-mcp-server has a Cursor installation link in its README. Cursor can connect using the provided MCP configuration, which runs the package through `npx`.

No, direct station lookup does not resolve three-letter IATA codes. Use the station's four-character ICAO-style registry identifier, or search by state or bounding box; returned records may include IATA and FAA aliases.

Yes, PIREP searches can filter by minimum and maximum altitude in feet MSL. The supported range is 0 to 60,000 feet, and reports with unknown altitude are excluded when an altitude bound is set.

Related MCP servers

All in Aerospace & Astrodynamics All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAviation Weather MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aviation-weather-mcp-server?style=directory)](https://allmcps.com/mcp/aviation-weather-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/aviation-weather-mcp-server"><img src="https://allmcps.com/api/badge/aviation-weather-mcp-server?style=directory" alt="Aviation Weather MCP Server on AllMCPs" /></a>