preflight-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAA_NOTAM_CLIENT_ID | No | FAA NOTAM API client ID. Required for get_notams tool. Obtain from https://api.faa.gov. | |
| FAA_NOTAM_CLIENT_SECRET | No | FAA NOTAM API client secret. Required for get_notams tool. Obtain from https://api.faa.gov. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_metar_tafA | Fetch decoded current METAR observations and TAF forecasts for one or more ICAO airport identifiers, satisfying the 14 CFR 91.103(a) requirement to review available weather reports and forecasts. An airport id found in only one of METAR/TAF is returned with the other field null (not an error); an id absent from both is listed in notFound. |
| get_airport_infoA | Fetch runway lengths/widths/surfaces and field elevation for a single ICAO airport identifier, satisfying the 14 CFR 91.103(b) requirement to know runway lengths at airports of intended use. Throws a clear error if the airport id is unknown. |
| aircraft_performanceA | Compute takeoff or landing ground roll and total distance over a 50ft obstacle for a Cessna 172R/S (Lycoming IO-360), satisfying the 14 CFR 91.103(b) requirement to know takeoff/landing distance data. Seeded with approximate POH-style performance data — see tool warnings for extrapolation/approximation caveats. |
| estimate_fuelA | Compute trip fuel, Part 91 reserve fuel, and a go/no-go fuel margin for a route, satisfying the 14 CFR 91.103(a) requirement to consider fuel requirements. This is a basic burn-rate x time model (no climb/descent profile). Distance per leg must be supplied directly, or derived by the caller from get_airport_info coordinates first. |
| find_alternatesA | Find alternate airports near a given airport that currently meet minimum ceiling/visibility, satisfying the 14 CFR 91.103(a) requirement to consider alternatives if the flight cannot be completed as planned. IMPORTANT: this tool has no bulk geo-radius search — you must supply candidateAirportIds (nearby airports you already know from route context); it does not discover candidates on its own. |
| get_notamsA | Fetch current NOTAMs for an airport from the FAA NOTAM Search API, satisfying the 14 CFR 91.103 requirement to review all available information. Requires FAA_NOTAM_CLIENT_ID and FAA_NOTAM_CLIENT_SECRET to be set in this server's environment (register at https://api.faa.gov); returns a clear 'not configured' error if they're unset rather than silently omitting NOTAMs from a briefing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/eddiehale3/preflight-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server