Toward reliable AI for aviation.
We are releasing the first version of the Community Aviation MCP, a connector that exposes weather and NOTAM data to Claude Desktop for general aviation pilots, an early, intentionally limited release.
MCP v1.0. A connector for Claude Desktop with five tools.
Ask Claude in natural language. Claude calls the tool it needs, receives the data, and composes a response. The MCP authenticates against your existing Community Aviation account, which means your home airport and identity flow into the conversation without per-session re-explanation.
Current conditions sourced from aviationweather.gov
Terminal forecasts, with proxy-station fallback when the requested airport does not issue its own
NWS Area Forecast Discussion for the region
Current notices sourced from the FAA
Frequencies, runways, fuel availability, FBO contacts, and services from the FAA archive
The work that needs to be done.
General aviation pilots have begun using large language models in their preflight workflows. The problem is that general-purpose language models, when handed aviation data without domain calibration, exhibit predictable failures.
They drift toward go/no-go recommendations under conversational pressure. They fabricate procedural numbers — approach minimums, climb gradients, frequencies — when asked for precision the underlying data does not directly provide.
The pilot asking is it safe to fly? is not asking a question a general model can reliably answer. The answer requires integration of weather, NOTAMs, aircraft performance, pilot currency, and judgment about consequence. The work lives between the model and the pilot — a knowledge engine that grounds responses in authoritative data, carries the calibrated voice of the right-seat companion, and surfaces failure modes honestly so the pilot retains command. The Community Aviation MCP is its first public artifact.
What v1 does not do.
We are explicit about the scope to address these failure modes:
- No approach plate retrieval, no procedure data. The fabrication risk is real and we are not exposing it until we can ground it against verified sources.
- No route synthesis. v1 reports two airports; it does not reason about the airspace between them.
- No deep personalization. The MCP knows your home airport. It does not know your last flight, last review, or currency event.
Fly the Airplane.
You are pilot in command.
What happens next.
Tools will be added to the MCP continually. Subsequent versions will include more weather layers (PIREPs, SIGMETs, AIRMETs, area forecasts, winds aloft), then route reasoning, and integration with Community Aviation's knowledge engine. The cadence is shaped by what we learn from the v1 release and user base, not by a fixed timeline.
Installing v1.
This connector is currently available as a custom install while our submission to the Anthropic Connectors Directory is under review. For pilots using Claude Desktop on a Pro or higher plan:
- In Claude Settings, navigate to Connectors → Add custom connector
- Enter the Community Aviation MCP URL:
[MCP URL] - Sign in to your Community Aviation account and set your home airport