Aviation Weather MCP Server

Created By
finacka year ago
MCP Server for Aviation LLM interactions
Overview

What is Aviation Weather MCP Server?

The Aviation Weather MCP Server is a Model Context Protocol (MCP) server designed to provide aviation weather information for flight planning by connecting to the Aviation Weather API to fetch METARs, TAFs, PIREPs, and other relevant data.

How to use Aviation Weather MCP Server?

To use the server, clone the repository, install the dependencies, build the server, and start it. You can then connect it with Claude for Desktop to ask weather-related queries.

Key features of Aviation Weather MCP Server?

  • Type-safe API client generated from the Aviation Weather API Swagger definition.
  • Tools for fetching current weather observations, terminal aerodrome forecasts, pilot reports, and route weather.

Use cases of Aviation Weather MCP Server?

  1. Fetching current weather at specific airports.
  2. Obtaining terminal aerodrome forecasts for flight planning.
  3. Accessing pilot reports for real-time weather updates near airports.

FAQ from Aviation Weather MCP Server?

  • Can I use this tool for flight planning?

No, this tool is not FAA-approved and should not be used as the sole source for flight planning or in-flight decision making.

  • What data does the server provide?

The server provides METARs, TAFs, and PIREPs sourced from aviationweather.gov for informational purposes only.

  • Is there a cost to use the Aviation Weather MCP Server?

The server is free to use, but always verify critical weather information through official channels.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
finack
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago