AI Agents for Flight Schools

Once connected, an agent can list and open the same records your staff work with every day:

• Schedule: reservations and the comments on them, plus completed flights with Hobbs, Tach, route, and instruction times.
• People: customers and instructors.
• Fleet and maintenance: aircraft, squawks, work orders, inspections, inventory, and reminders.
• CRM: leads, with status, source, notes, and follow-up dates.
• Reports: the list of report types, which the agent can then run for a date range.
• Team chat: the channels in your school's Team Chat.

That covers the questions an owner or chief instructor asks most often: "Which aircraft have open squawks?", "Who flew N123AB last week?", "How many discovery flight leads came in this month and how many booked?" The agent works from your data, so the answer is only as current as your schedule.

Write tools change data, so each one is narrow and does one job:

• Create, update, or cancel a reservation (change times, aircraft, people, or activity).
• Complete a flight from a reservation with Hobbs start and stop, optional Tach, route, and landings. Aircraft times update the same way they do when an instructor completes the flight.
• Set current Hobbs and Tach on an aircraft.
• Add a document to an aircraft, or log a fuel reimbursement on a reservation with the receipt.
• Add a note to a lead, or email a lead from the school's address.
• Run a report for a date range.
• Create a work order, which blocks the schedule and sets the aircraft to Maintenance.
• Draft an invoice for a completed flight. Drafts are never sent or charged by the agent; your staff review and send them.
• Post a message to Team Chat.

There are no tools for charging cards, issuing refunds, or changing settings.

An admin opens Settings → Integrations, picks Connect with your agent, and clicks Connect. Sky Schedule creates the school's key and copies the setup for you: the steps for adding a custom connector in Claude, and a JSON config for Cursor, Grok, and Claude Desktop. Paste it in and the agent can start using the Sky Schedule tools. There is no separate sign-in: the agent sends the school's API key as a bearer header on every request.

The key acts for the whole school, so treat it like a password and only share it with agents you trust. If a key ends up somewhere it shouldn't, Rotate issues a new one and Disconnect removes access completely.

Limits are per school and reset at midnight UTC:

• 1,000 MCP requests a day.
• 200 of those can be writes.
• The REST API has its own limit of 100 requests a day.

Sky Schedule writes each tool call to an audit log with the tool name, a trimmed summary of what was sent (secrets and file contents are redacted), and whether it worked.

Admins and instructors can ask Arlo about the school in plain English. Arlo can pull today's flights, upcoming reservations, a student's or instructor's details, aircraft status, invoices, flight history and tracks, documents expiring soon, current weather for an airport, and the numbers behind your report charts. When a student says they can't book, Arlo can check the school's rules and tell you what's blocking them.

Arlo proposes and you approve. Ask it to book a flight, email a student, email a whole group, set up onboarding, or publish a CRM form, and it shows you the proposal first. Nothing happens until you say yes. Each person gets 5 new Arlo prompts a day, and confirming a proposal never counts.

Two more features build on Arlo:

• Arlo Watch is opt-in. A few times a day it checks what's booked against what's due: an inspection that will run out before Thursday's flight, a grounding squawk on an aircraft with bookings, a medical that expires before a student's next lesson, invoices sitting unpaid, or an airplane with an empty week. Findings arrive in a pinned chat, and admins can get a morning briefing email when there's something to say.
• Workflows turn a sentence into an automation, such as "every morning at 6, email me a PDF of inspections due this month." Each workflow has a trigger, what to find, and what to do. Test runs only send to you, every live run is logged step by step, and Workflows never touch billing.

For your own dashboards and scripts, Sky Schedule has a read-only REST API. Create a key, send it in a header, and pull reservations, flights, customers, instructors, comments, work orders, squawks, inspections, inventory, and reminders. Aircraft and CRM leads are only available through the MCP tools, not the REST API. Requests return up to 100 records at a time, and the API uses the same school key as the MCP connection, so rotating one rotates both. The developer docs list every endpoint and field, and flight school reporting covers what you can get without writing any code.