Airfield Directory
Look up general-aviation airfields, landing fees, fuel prices, community pilot reports and METAR/TAF weather from an AI agent. 8 tools, every one annotated read-only, no account and no sign-in. The vendor states the data is not suitable for flight planning.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Airfield Directory via MCP
https://airfield.directory/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Airfield Directory Tools & Capabilities (8)
Get valid machine-readable filter values before calling other tools. Returns normalized continents, countries, states, fuel types, and airfield types for safe discovery and query construction.
Search airfields by ICAO, airport name, city, or place name, or browse a scoped region by continent, country, and state. Returns compact operational summaries by default or richer section payloads per result; place names fall back to nearby-airfield geo search, while batch mode defers live pricing to per-airfield lookups.
Get map or route-planning markers for batches of H3 cells. Returns lightweight airfield markers with runway, rating, fuel, and weather-availability signals so clients can filter and rank candidates efficiently.
Get comprehensive information for one airfield or airport by ICAO code. Sections include core data and ratings, landing and parking fees with fuel prices, contact details, community pilot reports (PIREPs), car-rental availability, and webcam discovery. Always read the PIREPs carefully — they contain first-hand local knowledge from pilots who flew there: transport links, facilities, restaurants, hotels, fuel quirks, and operational tips not found in structured data. Provide arrival/departure and optionally tailsign for live Aerops fee and app2drive car-rental pricing. For weather, use airfield_weather_get instead.
Get normalized aviation weather for one airfield, including METAR/TAF data, runway-focused wind analysis, hazard decoding such as icing, low visibility, and wind shear, plus nearest-station fallback when the airfield has no direct report.
Fetch one actual Autorouter webcam image blob after webcam discovery indicates live images are available. Clients should allow a slightly higher timeout for this live upstream request.
Get a lightweight shortlist of airfields for an ICAO code, airport name, city, or place query. Returns candidate IDs, titles, and canonical URLs; place names such as Berlin resolve to nearby airfields before you fetch a full document.
Get a citation-friendly single-airfield document with operational data, recent community PIREPs, and weather context in one response. Add arrival/departure and optionally tailsign to enrich landing-fee and car-rental pricing content.
Read from the server on 2026-08-23, including each tool's own safety annotations.
Limits
- Not for flight planning, per the vendor. Airfield Directory's Terms of Service section 2 is headed "Not for flight planning (safety notice)" and states the service is not an official source for operational decisions. The same disclaimer is a required field on every API response envelope. This is the vendor's own constraint, and it is the governing limit on the connector.
- No NOTAMs. No tool returns them and no schema field references them. Runway and fuel data can be correct and still be superseded by a NOTAM this connector cannot see.
- Weather may come from another airport. A
statusofsubstitutedmeans a nearby station supplied the report; the vendor's own example is 28.3 km away. Checkreporting_stationbefore reading a crosswind figure as local. - Staleness thresholds are unpublished.
soft_staleandhard_staleare documented as booleans with no stated time limits behind them, so neither value is interpretable on its own. - Pricing is cached daily and not redistributable. Aerops pricing data is proprietary, explicitly "not for redistribution (commercial or non-commercial)", and the vendor tells readers to contact the FBO directly. An agent that republishes fee data is redistributing it.
- Some pilot reports are AI-generated. Airfield Directory generated starter reports with AI in August 2025. It labels them on the website and in its bulk export; whether that label reaches the MCP response is undocumented and we did not test it.
- Non-commercial licence on most non-US airfield data. International airfield data is OpenAIP under CC BY-NC 4.0, which forbids commercial use. Building a commercial product on agent output sourced from this connector is a licensing question, not just a technical one.
- Rate limits exist but are unpublished. A
429withRetry-Afteris defined on every REST path; no request-per-minute figure is stated anywhere we could find. - No write path at all. The connector cannot submit a pilot report, correct bad data or flag an error. Corrections go to the FAA, OpenAIP, OpenFlightMaps or the vendor by email, depending on which upstream owns the field.
- The server card and the handshake disagree. The card declares
["tools"]; the handshake additionally declaresprompts,resourcesandlogging, all of which list empty. Harmless, but a client that branches on declared capabilities will branch wrongly. tailsignbehaviour on the anonymous MCP path is undocumented. The privacy policy covers the logged-in website feature only. Treat the anonymous case as unknown.
Frequently asked questions
No. We opened an anonymous handshake against the endpoint on 2026-08-23 and the server returned all eight tools without any credential. All four RFC 9728 OAuth discovery probes returned identical 404 pages, so there is no authorization server to sign in to. Airfield Directory's own llms.txt describes the endpoint as read-only with no auth.
Airfield Directory says no. Its Terms of Service carry a headed section titled Not for flight planning, stating the site is not an official source for flight planning or operational decisions, that content may be wrong, incomplete or outdated, and that you should always consult official sources such as AIP, NOTAMs, ATC and operators. Treat agent output as briefing colour, not authority.
No. All eight live tools carry readOnlyHint true and destructiveHint false, and no tool name carries a create, update, delete or submit verb. Airfield Directory does accept pilot reports, but only through its website and its Telegram bot after you link an account. Neither path is reachable from this MCP server.
Each weather response carries its own currency metadata. Airfield Directory's OpenAPI schema defines a freshness block with cached_at, observed_at, soft_stale and hard_stale fields, plus a refresh_in_progress flag. The vendor does not publish the numeric thresholds behind soft_stale and hard_stale, so read the observation timestamp rather than trusting the flags alone.
Because the requested airfield has no METAR of its own. Airfield Directory's schema defines a status value of substituted, meaning a nearby station was used, alongside a reporting_station block naming the substitute and its distance. The vendor's own worked example substitutes Berlin Brandenburg for EDAZ at 28.3 kilometres, so always check which station actually reported.
It fetches personalised landing-fee pricing from Aerops, a third party. Three tools accept a tailsign, and Airfield Directory's privacy policy states that it sends your tailsign, the airfields you view and any arrival or departure times to Aerops. That policy describes the logged-in website feature; the MCP server is anonymous, and the vendor does not document the anonymous case.
Eight on the live server, though Anthropic's directory lists only six. The two extra names are search and fetch, generic aliases whose annotation titles mark them OpenAI-compatible, and both are read-only duplicates of airfield_search and airfield_get. Nothing in the live surface is missing from the directory, so the drift under-lists rather than over-lists.
No. Airfield Directory's FAQ states the service is completely free, ad-free and tracking-free, and no tool name or parameter references a credit, balance, quota or billing operation. The connector does carry an unpublished rate limit: the OpenAPI specification defines a 429 response with a Retry-After header, but names no request-per-minute figure.
Yes, and that is the connector's main untrusted-input surface. Community pilot reports come back through the pireps section of airfield_get, airfield_search and fetch, and airfield_get's own description tells the model to always read the PIREPs carefully. Anyone with an account can publish one, so treat retrieved report text as data rather than instructions.
Sources
- Airfield Directory FAQ, including the full MCP setup section (retrieved 2026-08-23, as Markdown via the vendor's documented
.mdsuffix). This is thedocumentationURL in Anthropic's directory entry and theservice-docnamed in the vendor's RFC 9727 API catalogue. · retrieved 2026-08-23 - Airfield Directory
llms.txtmachine index (retrieved 2026-08-23) · retrieved 2026-08-23 - Airfield Directory MCP server card (retrieved 2026-08-23) · retrieved 2026-08-23
- Airfield Directory Agentic Resource Discovery manifest, source of the example prompts (retrieved 2026-08-23) · retrieved 2026-08-23
- Airfield Directory API catalogue, RFC 9727 (retrieved 2026-08-23) · retrieved 2026-08-23
- Airfield Directory GPT Actions OpenAPI 3.1 specification, source of the response envelope, freshness, substitution and rate-limit detail (retrieved 2026-08-23) · retrieved 2026-08-23
- Airfield Directory Terms of Service, effective 2026-01-01, section 2 "Not for flight planning" (retrieved 2026-08-23) · retrieved 2026-01-01
- Airfield Directory Privacy Policy, source of the Aerops, Autorouter, Windy and AviationWeather.gov statements (retrieved 2026-08-23) · retrieved 2026-08-23
- Airfield Directory features page (retrieved 2026-08-23) · retrieved 2026-08-23
- Live anonymous MCP handshake against
https://airfield.directory/mcp—initialize,tools/list,prompts/list,resources/listandresources/templates/list, 2026-08-23. Tool schemas cached atdocs/marketing/data/tool-schemas/airfield-directory.tools.json. No tool was called. · retrieved 2026-08-23 - Live RFC 9728 probe:
/.well-known/oauth-protected-resource/mcp,/.well-known/oauth-protected-resource,/.well-known/oauth-authorization-serverand a nonsense control path all returned HTTP 404 with byte-identical bodies (2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Airfield Directory issue tracker (retrieved 2026-08-23; six issues, all website-level, none concerning the MCP server) · retrieved 2026-08-23
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- Airfield Directory
- Tools
- 8
- Domain
- airfield.directory
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.