Dronelytics MCP is an MCP (Model Context Protocol) server for the Dronelytics drone mission planning platform, released as the npm package @dronelytics/mcp. Its positioning is to enable AI assistants to query U.S. drone airspace, plan missions, manage drone configurations, and export flight plans. The official description calls it the first drone platform built for AI agents, offering a total of 24 tools covering airspace queries, mission generation, Part 107 compliance, and flight plan export.
In terms of purpose, this service is mainly aimed at pre-flight intelligence and mission planning for drone flights within the United States, helping users use AI assistants to complete airspace restriction checks, survey flight plan generation, Part 107 compliance checks, pre-flight briefings, and flight plan export in KML/GPX format.
Its main capabilities revolve around its toolset. Airspace intelligence is implemented by the check_airspace tool, which can query 11 FAA data layers in a single call: UASFM altitude limits (maximum altitude grid from the FAA UAS Facility Map), Class airspace (Class B, C, D, E2, E3, E4 controlled airspace boundaries), TFR (active temporary flight restrictions, refreshed every 15 minutes), NOTAM (notices to air missions, with proximity filtering support), special use airspace (prohibited areas, restricted areas, MOA, warning areas), NSUFR (National Security UAS Flight Restrictions), stadiums (stadium TFR areas within 3 nautical miles), FRIA (FAA-recognized identification areas for recreational flyers), airports (nearby airports with distance and type), Mode C veil (transponder requirement areas within 30 nautical miles of major airports), and military training routes (low-altitude military flight corridors). All data comes from FAA ArcGIS services and is automatically refreshed. In addition, it also provides tools related to mission management and mission generation, as well as flight plan export functionality.
In terms of usage, users first need to generate an API key in Settings > API Keys at hub.dronelytics.io, and then configure the MCP client. The configuration file for Claude Desktop is located at ~/Library/Application Support/Claude/claude_desktop_config.json; Claude Code uses the project's .mcp.json or the global ~/.claude/.mcp.json; Cursor and Windsurf use the same npx configuration in MCP settings. Environment variables and the specific parameters of each tool are provided in the official documentation.
Applicable scenarios include: querying whether a drone can be flown at a specific location (such as the Golden Gate Bridge), generating a grid survey mission at a specified altitude (such as 200 feet) for a specific parcel (such as 10 acres), generating a pre-flight briefing for a building survey mission, exporting a labeled mission as KML, querying airports within 5 nautical miles of a coordinate, and validating a flight plan for a specific time and location (such as flying at 300 feet at the Statue of Liberty at 2 o'clock the next day), etc.
In terms of limitations, the materials only state that the service targets U.S. airspace and that the data comes from FAA ArcGIS services; information beyond fees, pricing, platform compatibility details, effects, and actual usage steps is not currently provided.
