Airfield Directory

Look up airfields, landing fees, fuel prices, pilot reports and METAR/TAF from an AI agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Airfield Directory connector does

The Airfield Directory MCP server connects a free, community-run general-aviation airfield database to Claude, ChatGPT and any MCP-compatible agent. Eight live tools look up airfields by ICAO code or place, return landing fees, fuel prices, community pilot reports, METAR and TAF weather, and webcam images. No account, no sign-in, no cost.

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.

Airfield Directory tools (8)

  • taxonomy_listRead-only

    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.

  • airfield_searchRead-only

    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.

  • airfield_list_by_h3Read-only

    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.

  • airfield_getRead-only

    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.

  • airfield_weather_getRead-only

    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.

  • airfield_webcam_imageRead-only

    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.

  • searchRead-only

    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.

  • fetchRead-only

    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 status of substituted means a nearby station supplied the report; the vendor's own example is 28.3 km away. Check reporting_station before reading a crosswind figure as local.
  • Staleness thresholds are unpublished. soft_stale and hard_stale are 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 429 with Retry-After is 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 declares prompts, resources and logging, all of which list empty. Harmless, but a client that branches on declared capabilities will branch wrongly.
  • tailsign behaviour 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

Does the Airfield Directory MCP server need an account or an API key?

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.

Can I use Airfield Directory data for actual flight planning?

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.

Can the Airfield Directory connector write anything, or post a pilot report?

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.

How current is the weather the Airfield Directory MCP server returns?

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.

Why does the weather sometimes come from a different airport?

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.

What does the tailsign parameter do, and who receives it?

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.

How many tools does the Airfield Directory MCP server have?

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.

Does anything on the Airfield Directory connector cost money or spend credits?

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.

Can text written by other pilots reach my agent through this connector?

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

More Data & Research connectors

  • Airtable

    Read, write and restructure Airtable bases from your AI assistant.

  • alphaXiv

    Search, read and analyse arXiv papers from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Airfield Directory to work.

Connect Airfield Directory once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.