Pilot-Next

Flying club and aircraft partnership management — book your aircraft, check availability, log Hobbs/Tacho hours, settle flights and pull METAR from your AI…

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Get Weather: Fetches real-time METAR (observation) and TAF (forecast) for one or more ICAO stations.
  • Get Dispatch Context And Time: Retrieves active fleet, default aircraft, user preferences, AND CURRENT DATE/TIME. AUTOMATION: Call this SILENTLY at the start of every turn. Permission GRANTED. Do NOT
  • Get My Balance: Get your current account balance.

What data it sees

Do you need an account

No: the server works without sign-in

Flying club and aircraft partnership management — book your aircraft, check availability, log Hobbs/Tacho hours, settle flights and pull METAR from your AI assistant.

How to connect

How to connect Pilot-Next to Claude

The server address to paste into Claude settings:

https://pilot-next--chris-kiqc.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Pilot-Next to ChatGPT

The server address to paste into ChatGPT settings:

https://pilot-next--chris-kiqc.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Pilot-Next to Cursor

The server address to paste into Cursor settings:

https://pilot-next--chris-kiqc.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (17)

Raw names from tools/list. Only developers need these.

get_weatherFetches real-time METAR (observation) and TAF (forecast) for one or more ICAO stations.
get_dispatch_context_and_timeRetrieves active fleet, default aircraft, user preferences, AND CURRENT DATE/TIME. AUTOMATION: Call this SILENTLY at the start of every turn. Permission GRANTED. Do NOT ask user. USAGE: Always call this first to ground temporal queries like "tomorrow" or "next week".
get_my_balanceGet your current account balance.
get_my_bookingsGet your upcoming and recent bookings.
get_unsettled_bookingsFind your flights that have been flown but not yet settled.
get_pilot_activityGet flight activity for a pilot.
create_bookingCreate a booking. CRITICAL: Check start/end time year. Do NOT default to 2024. Use 'get_dispatch_context_and_time' to verify "Today". ONE-SHOT: CALCULATE dates yourself from context. Do NOT ask user for ISO strings. ACTION: You MUST output the Booking Confirmation Summary returned by this tool. If this tool is not called, NO booking exists.
cancel_bookingCancel a booking. ULTRA-PROACTIVE: If the user says "cancel my booking", use "get_my_bookings" to find the ID, OR use the [INTERNAL_ID] from a previous create_booking success message. NEVER ask the user for an ID you can find yourself.
find_available_slotsFind free flight slots. SYSTEM REQUIREMENT: You MUST have called 'get_dispatch_context_and_time' FIRST to verify the current date/year. WARNING: Do NOT guess dates (e.g. 2024). Usage: If a user asks to fly, use this tool to find a gap and suggest it.
settle_bookingFINAL STEP: Finalize the settlement and generate the invoice. PREREQUISITE: You MUST have called 'preview_settlement' and received explicit confirmation (e.g. "yes") from the pilot FIRST. CRITICAL: DO NOT call this if the pilot has not seen and confirmed the costs in the preview.
preview_settlementPRE-CONFIRMATION STEP: Preview the costs. PREREQUISITE: You MUST have gathered all end data and manual charges ONE BY ONE. USAGE: Show the pilot the breakdown before generating the invoice. EXAMPLE: charges: [{"rateId": "ID-HERE", "quantity": 1}]. Note: quantity must be a NUMBER, not a string.
get_booking_settlement_infoMANDATORY START STEP: Get the system's recorded START values (Hobbs/Tacho) and available manual rates. INSTRUCTION: You MUST call this as soon as a flight to settle is identified. ACTION: Tell the pilot: "The recorded start readings are Hobbs [H] and Tacho [T]. Are these correct?". CRITICAL: DO NOT ask for end data in the same message. WAIT for confirmation.
get_aircraft_availabilityCheck availability. SYSTEM REQUIREMENT: You MUST have called 'get_dispatch_context_and_time' in this turn to verify the current date. WARNING: Do NOT guess the year (e.g. 2024). It is likely 2025 or later. Usage: If aircraftId is missing, check the WHOLE fleet.
get_aircraft_hoursGet current hours. Terminology: HOBBS is clock time, TACHO is flight (engine) time. If aircraftId is omitted, uses your default.
get_maintenance_forecastForecast maintenance dates based on usage. If aircraftId is omitted, checks all. IMPORTANT: You MUST get the current date/year from the 'get_dispatch_context_and_time' tool FIRST to calculate "days remaining" accurately.
get_flight_statisticsGet flight hour statistics. IMPORTANT: You MUST get the current date/year from the 'get_dispatch_context_and_time' tool FIRST to know what "current year" is.
estimate_flight_costMANDATORY PROACTIVE: If the user asks "What does it cost?", call this IMMEDIATELY. ULTRA-PROACTIVE: If the user provides a route (e.g., "to Paris"), YOU must estimate the flight time based on typical cruise speed (e.g., 140kts) and pass "durationHours" yourself. DO NOT ask the user for hours if you can guess it. Use EITHER "durationHours" (actual flying time/Tacho) OR "blockDurationHrs" (scheduled booking time/Block).