
Mcp Metar
io.github.daedalusPublished by GitHub account daedalusv0.1.0Updated Oct 24, 2026
MCP server for METAR/TAF aviation weather data
Overview
Fetches METAR and TAF aviation weather reports for an airport by its ICAO code.
- What you can do
- This MCP server exposes three tools for aviation weather: get_metar returns the current METAR observation for an airport, get_taf returns the Terminal Aerodrome Forecast, and get_airport_weather returns both together. Airports are identified by ICAO code, for example KJFK. The package also exposes the same functions for direct Python use.
- When to use it
- Useful when an assistant needs current or forecast airport weather, such as flight planning, briefing, or answering questions about conditions at a specific airport. It is a narrow, single-purpose server, so add it only if aviation weather lookups are part of the workflow.
- Requirements
- Runs locally as a stdio process, installed from PyPI as mcp-metar (pip install mcp-metar), so a Python environment is needed. No authentication, environment variables, or headers are declared. Network access is implied by fetching weather data.
Installation
In SourceWeft
- Open Mcp Metar in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-metar
MCP server for METAR/TAF aviation weather data
[PyPI] [Python] [Coverage] [Ruff]
mcp-name: io.github.daedalus/mcp-metar
Install
Usage
MCP Server
This package provides an MCP server that can be used with MCP-compatible clients. Configure your client with:
Available Tools
get_metar: Fetch current METAR weather data for an airport by ICAO codeget_taf: Fetch TAF (Terminal Aerodrome Forecast) for an airport by ICAO codeget_airport_weather: Fetch both METAR and TAF for an airport by ICAO code
Development
License
MIT
Source: README.md at commit 16c1ef9
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts