Skip to main content
Glama

FPV Airspace

An MCP server and map that answer the question existing airspace tools do not: can I legally take off and fly a drone here, in the UK?

Airspace restriction data is the easy half. A UK pilot actually has to clear three layers: permanent airspace restrictions (aerodrome flight restriction zones, prohibited, restricted and danger areas, the 400 m zone around every prison), temporary restrictions (NOTAMs), and landowner rules (National Trust byelaws, Forestry England permits, council park byelaws). The practical workaround pilots use is launching from a public right of way, where no landowner permission is needed. This server puts all of that behind thirteen tools that take a place name, a postcode or coordinates, covers England, Wales, Scotland and Northern Ireland, and draws it on a map that Claude can show inline or that you can open on a phone.

Informational only. It is not a substitute for a NATS pre-flight briefing, the CAA Drone Code, or permission from the landowner and any relevant aerodrome.

Sponsor

FPV Airspace is free and stays free: the data licences it relies on are for non-commercial use, so nothing is ever paywalled. If it saves you a wasted trip, a one-off donation, a monthly donation or sponsoring on GitHub helps cover the hosting and the weather API.

What it answers

  • Is this point inside a restriction? check_location: a one-line verdict and every zone containing the point, prisons included.

  • What is this aerodrome's zone? get_aerodrome_zone by name or ICAO code.

  • Is there a NOTAM in force? check_notams from the live NATS bulletin; unplaceable NOTAMs are listed, never dropped.

  • What does my route cross? check_route for waypoints or an area, with the distance at which each zone is entered.

  • Can I take off here? check_takeoff_site: nearest rights of way, parking, ground hazards, landowner rules, access land, designations and the council at the point.

  • Where can I park? find_parking from OpenStreetMap, nearest first.

  • Can I fly here, now? preflight_briefing: one GO, CAUTION or NO-GO with reasons from airspace, NOTAMs, weather, geomagnetic activity, paths, parking and your drone's rules.

  • What is the ground doing? check_terrain against the 120 m rule along a route or around a point.

  • Where could I take off? find_takeoff_spots scores and ranks candidate spots, and the map numbers them.

  • What can my drone do? check_drone_rules: subcategory, separation, registration and Remote ID under the CAA class mark rules.

  • Is the weather flyable? check_weather: hourly ratings against small-drone limits, plus the K-index.

  • Show me. Every location answer on the hosted server carries a map that Claude renders inline.

  • Plus geocode and get_data_status. Arguments and examples for each are in docs/tools.md.

Related MCP server: dronelytics

Quick start

Requires Node 22.13 or newer (the server uses Node's built-in SQLite, so there is nothing native to compile). The package is a single bundled file with no dependencies, so npx starts it in a few seconds.

npx -y fpv-airspace

Claude Desktop

Add to claude_desktop_config.json (Settings > Developer > Edit Config):

{
  "mcpServers": {
    "fpv-airspace": {
      "command": "npx",
      "args": ["-y", "fpv-airspace"],
      "env": {
        "OS_NAMES_API_KEY": ""
      }
    }
  }
}

OS_NAMES_API_KEY is optional. Without it, geocoding uses OpenStreetMap's Nominatim. With a free key from the OS Data Hub, Ordnance Survey place names are tried first.

On first use the server downloads the current airspace data pack (about 195 MB compressed, 527 MB on disk: 1,069 restriction zones, 520,000 rights of way, 94,000 landowner and designation polygons, 586,000 parking spots and 816,000 ground hazards) into ~/.cache/fpv-airspace and reports progress on stderr. NOTAM and geocoding tools work while it downloads. The pack is refreshed automatically when a new AIRAC cycle is published.

Claude Desktop extension (.mcpb)

Each release also ships fpv-airspace.mcpb. Download it from the releases page, double-click it, and Claude Desktop installs the server with its bundled Node runtime and a settings panel for the optional OS Names key.

Claude Code

claude mcp add fpv-airspace -- npx -y fpv-airspace

Remote connector (Claude web, mobile and voice)

The same server runs as a Cloudflare Worker at https://fpv-airspace.fetchlabs.co.uk/mcp, which is what Claude's mobile app and voice mode can reach: they cannot run local servers, only remote connectors. Add it on claude.ai under Settings > Connectors > Add custom connector with that URL, and it becomes available on every surface, including voice conversations. Every tool accepts format: "brief", which returns two or three spoken-friendly sentences instead of the full report.

Running your own copy, on Cloudflare or as plain streamable HTTP or Docker, is covered in docs/hosting.md.

The map

Search a place, tap the map or use your position; every zone, NOTAM, path, landowner rule, parking spot and ground hazard in view is drawn with its own icon, a long press lists what is under a point, the card shows the coming week's flyability hour by hour, and the overlays load as you pan. Claude renders the same map inline with an answer. The Plan button turns the map into a flight planner: tap out waypoints with heights, see which sit inside a restriction, and download the plan as a DJI Fly waypoint mission (.kmz) or KML. The full guide, with the layers key and more screenshots, is in docs/map.md.

Documentation

  • Tools: every tool, its arguments and example prompts.

  • The map: search, layers, hazards, weather, the flight planner and DJI Fly export, the phone layout and URL parameters.

  • Data sources and attribution: where each layer comes from, how often it refreshes and under what licence.

  • Configuration: environment variables for the server and the build.

  • Hosting: Cloudflare Worker, streamable HTTP and Docker.

  • Development: tests, packs and releases.

Caveats

  • Rights-of-way data is an interpretation of each council's Definitive Map, not the Definitive Map itself, and covers England and Wales. Scotland has no definitive map (access rights apply instead, and core paths need a Spatial Hub key) and Northern Ireland has no definitive map either: only councils that publish their asserted paths appear, so absence there means unknown; the tools say so.

  • The landowner rule layer holds National Trust and Forestry England land and a hand-curated list of council byelaws and policies. The National Trust's open data omits its Northern Ireland properties. Absence of a rule never means take-off is permitted.

  • Ground hazards and parking come from OpenStreetMap and are as complete as the map is; they are advisory and never change a verdict.

  • Only zones reaching below 400 ft (120 m) count towards a verdict; higher zones are listed on request.

  • NOTAMs are read from the NATS contingency bulletin, which may lag the live system by up to an hour.

  • ICAO codes for aerodromes come from a curated table covering major and well-known UK aerodromes; lookups by name always work.

Licence

MIT. Data sources carry their own licences; see the licences folder.

Available Tools

13 tools
check_drone_rulesCheck drone rulesA
Read-only

Which UK open category rules apply to a consumer drone: the subcategory (A1 fly over people, A2 near people, A3 far from people), the separation from uninvolved people, whether Flyer ID and Operator ID registration are needed, and when Remote ID is required. Give a model name from the catalogue (DJI, Autel, Potensic, HoverAir, Parrot) or a weight in grams plus any class mark. Rules follow the CAA class marks in force from 2026, including the EU C-class transition to the end of 2027.

Inputs: date, model, format, weight_g, +3 more.

check_locationCheck airspace at a locationA
Read-only

Check permanent UK airspace restrictions at a single point for drone flying. Give a place name or postcode, or lat/lon. Returns a one-line verdict, then every zone containing the point (aerodrome FRZ, prohibited, restricted, danger, other) with vertical limits, activation notes and contact, and any landowner rule at the point. Does not include NOTAMs; call check_notams for temporary restrictions.

Inputs: lat, lon, place, format, +1 more.

check_notamsCheck NOTAMs at a locationA
Read-only

Check temporary airspace restrictions (NOTAMs) from the NATS UK pre-flight bulletin that cover a point, optionally within a radius and on a given date. Returns each NOTAM with validity, radius and full text, sorted by distance. NOTAMs without usable coordinates are listed separately so nothing is silently dropped. Informational only; not a substitute for an official NATS pre-flight briefing.

Inputs: lat, lon, date, place, +3 more.

check_routeCheck airspace along a route or areaA
Read-only

Check permanent airspace restrictions along a drone route or across an area. Give either waypoints (at least two; each a [lon, lat] pair or a place name) or an area (bbox [west, south, east, north] or a GeoJSON Polygon). Returns the zones crossed, deduplicated, with the distance along the route at which each is first entered. Place-name waypoints are geocoded; ambiguous names are returned for you to resolve. For ground elevation along the route call check_terrain.

Inputs: area, format, waypoints, include_above_120m.

check_takeoff_siteCheck a take-off siteA
Read-only

Assess a potential drone take-off spot in the UK. Returns the airspace verdict at the point, the nearest public rights of way (footpaths, bridleways, byways) with distances and the responsible council, and any known landowner rule (National Trust and Forestry England land, council byelaw or policy) at the point, plus open access land and SSSI or National Park designations as context. A public right of way is a strong indicator of legal access; rights-of-way data covers England and Wales only.

Inputs: lat, lon, drone, place, +4 more.

check_terrainCheck terrainA
Read-only

Ground elevation along a route or around a point, against the 120 m rule: the 120 m limit is measured from the surface below the aircraft, so rising ground eats into clearance and falling ground can put a fixed-height flight above the limit. Give waypoints (2 to 50 places or [lon, lat] pairs) for a profile, or a place / lat and lon for the ground within radius_m. Reports the highest and lowest ground relative to the take-off point and warnings for the planned flight height. Elevations from Copernicus GLO-90 via Open-Meteo, about 90 m resolution.

Inputs: lat, lon, place, format, +4 more.

check_weatherCheck drone weatherA
Read-only

Drone-relevant weather forecast for a UK point from Open-Meteo: wind and gusts at 10 m, wind at 120 m, rain, visibility, cloud, temperature and daylight hours, with an advisory flyability rating per hour (good / caution / poor against typical small-drone limits). Give a place or lat/lon and optionally a date or date-time; defaults to the next few hours.

Inputs: lat, lon, date, hours, +2 more.

find_parkingFind parking near a locationA
Read-only

Find car parks, laybys and rest areas near a UK point, nearest first, from OpenStreetMap. Give a place name or postcode, or lat/lon. Returns name, type, distance, fee and access notes. Publicly accessible places only unless include_private is set.

Inputs: lat, lon, place, format, +3 more.

find_takeoff_spotsFind take-off spotsA
Read-only

Suggest take-off spots near a UK place: points on public rights of way, next to parking or on open access land, scored on the data held here. Spots inside prohibited, restricted, prison or aerodrome zones, or on land where take-off is banned, are excluded; NOTAMs, danger areas, landowner rules and ground hazards lower the score, paths, parking and access land raise it. Returns the best few with reasons and coordinates, and the map shows them numbered. A right of way is a right to pass, not to stop and fly.

Inputs: lat, lon, drone, place, +4 more.

geocodeGeocode a UK placeA
Read-only

Resolve a UK place name, postcode or landmark to coordinates. Use it to disambiguate before running a check when a name could match several places. Returns up to ten candidates with source and confidence.

Inputs: query (required), limit, format.

get_aerodrome_zoneLook up an aerodrome FRZA
Read-only

Look up a UK aerodrome's flight restriction zone (FRZ) by name or ICAO code, e.g. "Bristol" or "EGGD". Returns the zone centre, approximate radius, bounding box, vertical limits and contact, optionally with the GeoJSON geometry.

Inputs: aerodrome (required), format, include_geojson.

get_data_statusData status and attributionA
Read-only

Report the data behind this server: airspace pack version and AIRAC effective dates, when each source was fetched and its licence, NOTAM bulletin cache age, geocoding providers available, runtime details, and the attribution strings that must be shown to users.

Inputs: format.

preflight_briefingPre-flight briefingA
Read-only

One pre-flight briefing for a UK take-off point and time: a GO, CAUTION or NO-GO status with reasons, from the airspace verdict, live NOTAMs, the weather window, geomagnetic activity, rights of way, parking and, when a drone is named, its open category rules. A live source that cannot be read is reported as an outage, never assumed clear. Give a place or lat/lon; date and hours set the flying window (default now, 3 hours). Set frz_permission when an aerodrome has already agreed the flight.

Inputs: lat, lon, date, drone, +7 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct concern: permanent restrictions, NOTAMs, routes, takeoff sites, terrain, weather, rules, parking, suggestions, geocoding, and data status. No two tools overlap in purpose; even similar ones like check_location and check_takeoff_site differ in scope (airspace vs. access + designations).

    Naming Consistency4/5

    The vast majority follow a verb_noun pattern (check_*, find_*, get_*, geocode). 'preflight_briefing' breaks the pattern as a noun phrase, but it is the only deviation and is still clear and intuitive.

    Tool Count5/5

    13 tools is well-scoped for a drone airspace assistant, covering all essential operations without redundancy or bloat. Each tool serves a specific need, from preflight to parking.

    Completeness4/5

    The surface is highly complete for UK drone operations: permanent and temporary restrictions, takeoff site evaluation, route checks, terrain, weather, drone rules, parking, and suggestions. A minor gap is no direct NOTAM check along a route, but the point-based NOTAM with radius can be sampled. Overall no critical dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables flight planning and aviation operations through intelligent airport resolution, great-circle route calculation, and aircraft performance estimation. Supports 28,000+ airports worldwide and 190+ aircraft types for comprehensive flight planning via natural language.
      46
      64 PyPI
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      US drone airspace intelligence and mission planning. 24 MCP tools: check airspace restrictions across 11 FAA data layers, plan grid/orbit/corridor surveys, validate Part 107 compliance, generate pre-flight briefings, and export to KML/GPX/QGC/Litchi/WPML.
      25
      3
      MIT