uk-drone-airspace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP transport | 8080 |
| LOG_LEVEL | No | Log level: debug, info, warn, error, silent | info |
| PACK_PATH | No | Use a local pack and skip downloads | |
| OS_NAMES_URL | No | URL for the OS Names API | https://api.os.uk/search/names/v1/find |
| MCP_TRANSPORT | No | MCP transport: stdio or http | stdio |
| NOMINATIM_URL | No | URL for the Nominatim geocoder | https://nominatim.openstreetmap.org/search |
| NOTAM_PIB_URL | No | URL for the NATS NOTAM bulletin | https://pibs.nats.co.uk/operational/pibs/PIB.xml |
| HTTP_TIMEOUT_MS | No | Timeout for live HTTP calls in milliseconds | 8000 |
| OS_NAMES_API_KEY | No | Enables the OS Names geocoder | |
| PACK_STALE_HOURS | No | How often to check for a newer pack in hours | 24 |
| POSTCODES_IO_URL | No | URL for postcodes.io | https://api.postcodes.io |
| PACK_MANIFEST_URL | No | URL to the pack manifest; defaults to the latest GitHub release manifest | |
| PACK_UPDATE_CHECK | No | Whether to check for a newer pack in the background | true |
| NOTAM_CACHE_TTL_SECONDS | No | Cache TTL for NOTAMs in seconds | 1800 |
| DRONE_AIRSPACE_CACHE_DIR | No | Directory for the data pack and caches | ~/.cache/uk-drone-airspace-mcp |
| GEOCODE_CACHE_TTL_SECONDS | No | Cache TTL for geocoding in seconds | 2592000 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_locationA | 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. |
| get_aerodrome_zoneA | 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. |
| check_notamsA | 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. |
| check_routeA | 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. |
| check_takeoff_siteA | 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. |
| find_parkingA | 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. |
| check_weatherA | 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. |
| check_drone_rulesA | 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. |
| preflight_briefingA | 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. |
| check_terrainA | 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. |
| find_takeoff_spotsA | 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. |
| geocodeA | 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. |
| get_data_statusA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| map | Interactive map of restriction zones, NOTAMs, rights of way, landowner rules and parking around a point or route. |
TDQS
Scored across 13 tools
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).
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.
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.
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.