Airfield Directory provides searchable aviation facility data, enabling AI agents to find airports and airfields by name, location, identifier, and facility details. Retrieve runway information, geographic coordinates, and operational attributes to support flight planning and aviation research.
Claude is Anthropic's AI assistant, available as a desktop app and in Cowork. It supports custom connectors, so it can call MCP servers directly from a chat.
This guide connects Airfield Directory MCP to Claude Desktop through MewCP, so Claude Desktop can use Airfield Directory MCP's 8 tools, like taxonomy_list, airfield_search and airfield_list_by_h3.
Airfield Directory MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Crawl websites and extract clean structured data optimized for AI applications and automation. Collect content from the web at scale while maintaining high-quality outputs.
Extract structured data from websites and public web pages. Fetch content, parse information and transform online data into formats that can be consumed by applications, agents and workflows.
TinyFish MCP for running AI-driven browser automation tasks, deep web research, persistent browser login profiles, remote CDP browser sessions, and agentic wallet payments.
Scrape, extract, and understand the web, plus identify any company from a domain, email, name, or transaction string. This MCP server exposes Context.dev's API for web scraping in multiple formats (raw HTML, Markdown, screenshots, images, sitemaps, and web search), schema-driven structured data extraction, design-system extraction (styleguides and fonts), and brand intelligence lookups. It's built for AI agents that read, summarize, or monitor web content, for enriching CRM, KYC, or fintech pipelines with company and brand data, and for extracting a competitor's design system or structured product and pricing data at scale.
Other clients
Airfield Directory MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Airfield Directory MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In Claude, open Settings → Connectors, then choose Add custom connector.
Name it "mewcp" and paste the URL.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Get valid machine-readable filter values before calling other tools. Returns the requested taxonomy kind, applied filters, total count, and items: continent/state values, country codes and names, fuel IDs and names, or airfield-type IDs and codes.
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. Returns an MCP image content block plus structured metadata with the airfield ICAO, provider, selected index, total image count, and MIME type. 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 as JSON in a text content block. Returns the airfield ID, title, canonical URL, narrative text with operational data, recent community pilot reports (PIREPs) and weather context, plus location, facility, and rating metadata and an aeronautical disclaimer. Add arrival/departure and optionally tailsign to enrich landing-fee and car-rental pricing content.
