PlaneWXHelp
About PlaneWX

Connect PlaneWX to Claude, Grok, ChatGPT, Gemini and Perplexity

Connect PlaneWX to an AI assistant so you can ask for a WX Score and departure windows in chat. The pilot in command still makes every go or no-go decision.

Part of Pro Plus. Pro Plus features

PlaneWX has a plugin for both Claude and ChatGPT. Use each assistant's directory listing when you can.

Claude custom connector steps are further down on this page.

Claude: Find PlaneWX in Claude's connector directory.

ChatGPT: Add PlaneWX in ChatGPT. A paid ChatGPT plan is required.

This is a beta, so you may run into bugs. If something looks wrong, tell us with the Feedback button in the app.

The AI assistant connector is a Pro Plus Labs feature. Turn it on first under Profile, Preferences, PlaneWX Labs (the switch is labeled AI assistant connector). See PlaneWX Labs and Plans.

Who can use the connector

  • Plans: Pro Plus. This includes a Pro Plus trial. Free, Casual and Pro without a Pro Plus trial do not have it.
  • Turn on AI assistant connector under Profile, Preferences, PlaneWX Labs. The connector does not work for your account while that toggle is off.
  • Sign in: you sign in with your PlaneWX account when the assistant sends you to PlaneWX. If you are signed out, PlaneWX asks you to sign in first.

MCP server URL

Use this URL when your assistant asks for a custom MCP server or connector address:

https://app.planewx.ai/api/mcp
AI connector setting in Preferences
AI assistant connector setting.

How connecting works

  1. Turn on AI assistant connector under Profile, Preferences, PlaneWX Labs.
  2. In your assistant, add PlaneWX from its connector directory, or add a custom MCP server with this address: https://app.planewx.ai/api/mcp
  3. When the assistant opens PlaneWX, sign in with your PlaneWX account.
  4. PlaneWX shows a consent screen titled Allow, followed by the assistant's name. Read the permissions listed below, then choose Allow or Deny.
  5. Back in the assistant, ask for a WX Score or ask what your limits are.

Steps for each assistant are below. You can disconnect at any time.

Claude

Find PlaneWX in Claude's connector directory (listed as PlaneWX, Community, by PlaneWX LLC). Sign in to PlaneWX and choose Allow; tick Also allow building briefings if you want scored runs.

Or add it as a custom connector with the URL https://app.planewx.ai/api/mcp:

  1. Turn on the AI assistant connector first under Profile, Preferences, PlaneWX Labs (the switch is labeled AI assistant connector).
  2. Open Claude and go to Customize, then Connectors, then Add custom connector. Leave OAuth Client ID and secret blank. On Team and Enterprise, only Owners can add a custom connector. Free allows one custom connector.
  3. Enter the PlaneWX MCP URL (https://app.planewx.ai/api/mcp).
  4. Sign in with your PlaneWX account when prompted and tick Also allow building briefings on the PlaneWX consent screen to allow scored runs.
  5. Ask Claude a weather question for a route and time. The assistant calls PlaneWX tools such as resolve_airport, list_trips, get_trip_briefing, score_trip, or find_departure_windows. Ask "What are my limits?" and the assistant calls get_my_limits.

ChatGPT

Pro Plus Labs. PlaneWX scores the weather for your route and time; the pilot in command still makes every go or no-go decision.

Add PlaneWX in ChatGPT

A paid ChatGPT plan is required.

PlaneWX in ChatGPT

Gemini

  1. You need Pro Plus or a Pro Plus trial. Turn on the AI assistant connector in Profile, Preferences, PlaneWX Labs.
  2. Needs Gemini custom apps access: 18 or over, in the US, signed in with a personal Google Account, with Keep Activity on.
  3. On your computer, go to gemini.google.com. At the bottom, click Settings, then Connected Apps (if you don't see Connected Apps, click Personal Intelligence first). Under Custom apps, click Add a custom app, enter the URL https://app.planewx.ai/api/mcp and click Next.
  4. Leave Client ID and Client secret blank.
  5. Sign in to PlaneWX. Tick Also allow building briefings if you want scored runs, then press Allow.
  6. Disconnect anytime in PlaneWX account settings or in Gemini.

Grok

  1. Turn on the AI assistant connector first under Profile, Preferences, PlaneWX Labs (the switch is labeled AI assistant connector).
  2. Open Grok at grok.com. In settings, look for the option to add a custom connector or MCP server.
  3. Enter the PlaneWX MCP URL (https://app.planewx.ai/api/mcp).
  4. Sign in with your PlaneWX account when prompted, then choose Allow on the PlaneWX consent screen. Tick Also allow building briefings if you want scored runs.
  5. Ask Grok a weather question for a route and time. The assistant calls PlaneWX tools such as resolve_airport, list_trips, get_trip_briefing, score_trip, or find_departure_windows. Ask "What are my limits?" and the assistant calls get_my_limits.

Perplexity

Perplexity limits some custom MCP servers to its Pro, Max, or Enterprise plans.

  1. You need Pro Plus or a Pro Plus trial. Turn on the AI assistant connector in Profile, Preferences, PlaneWX Labs.
  2. In Perplexity, open Plugins in the sidebar (or Customize, then Connectors if Plugins is not there yet). Open Add custom, then Connector, then Add MCP connector, and select Remote.
  3. For Name, enter PlaneWX. For MCP Server URL, enter the PlaneWX MCP URL (https://app.planewx.ai/api/mcp).
  4. For Authentication, choose OAuth. PlaneWX registers Perplexity on its own, so no Client ID or Client Secret is needed. For Transport, choose Streamable HTTP.
  5. Check the acknowledgement box and click Add. PlaneWX appears on the Plugins page.
  6. Click the PlaneWX connector card to start sign-in. Sign in to PlaneWX. Tick Also allow building briefings if you want scored runs, then press Allow.
  7. Ask Perplexity a weather question for a route and time. The assistant calls PlaneWX tools such as resolve_airport, list_trips, get_trip_briefing, score_trip, or find_departure_windows. Ask "What are my limits?" and the assistant calls get_my_limits.

On Perplexity Enterprise, members can add a custom connector only after an admin turns on Allow members to add custom connectors (off by default). An admin can also add PlaneWX for the whole organization under Enterprise settings, Permissions, Connectors permissions, then + Custom connector, and share it with the organization from the Permissions screen. For an organization connector with OAuth, Perplexity lets the admin either sign in once for everyone or have each member sign in. Choose to have each member sign in, so every pilot connects their own PlaneWX account. Do not sign in once for the whole organization: that would share one PlaneWX account's trips, Self Debriefs (including private notes), FRATs and daily limit with every member. The rest of the steps are largely the same.

Once connected, Perplexity uses the same PlaneWX tools as the other assistants. Pilots ask things like:

  • What is the WX Score for KGDJ to 8V2 Saturday morning?
  • Find departure windows for KGDJ to 8V2 this weekend.
  • What does my saved KGDJ to 8V2 briefing say?
  • What are my limits?

To remove PlaneWX from Perplexity later, open the ellipsis menu on the connector card. Disconnecting in PlaneWX account settings works too.

What PlaneWX shares

When connected, PlaneWX can share your plan tier, home airport, aircraft (tail number, type, and per-aircraft minimums), personal minimums, MCP usage for today, your saved trips (upcoming, past, or all, including Self Debriefs with private notes up to 300 characters, or up to 400 characters when you ask for full details, and FRAT risk assessments), the stored briefing for a trip you ask about (same score the app shows), and scored candidate briefings you ask for in the chat.

PlaneWX never sends your password, payment details, medical certificate, logbook entries, or other pilots' data through this connector.

PlaneWX records each tool call your assistant makes (which tool, which assistant, whether it worked, how long it took, and when), but not what you asked or what came back.

Your saved trips (route, ETD, stored WX Score band, monitored or paused) come back without scoring again. Ask for a trip's stored briefing to see the same full briefing the app shows. Private notes from a Self Debrief are included and capped (up to 300 characters, or up to 400 characters when you ask for full details). If the list is long, ask the assistant for the next page. Example: "What upcoming trips do I have?"

When you ask your assistant about a saved trip, it reads the same briefing and WX Score you see in the app. A new score runs only when you ask your assistant to refresh.

Ask for past trips or all trips to see flown trips too, with the briefed WX Score at ETD, your Self Debrief (private notes included and up to 300 characters, or up to 400 characters when you ask for full details), and actual versus forecast when you have a post flight debrief. FRATs come with every trip. Example: "Show my FRATs where I chose no-go this year."

Permissions on the consent screen

The consent screen is titled Allow, followed by the assistant's name. It lists the app name, the return URL and the sign-in scopes the assistant asked for. It then reads:

The assistant's name will get access to your PlaneWX account through PlaneWX assistant tools. Those tools can read your profile, aircraft, personal minimums, saved trips, Self Debriefs (including private notes up to 300 characters, or up to 400 characters when you ask for full details), and FRATs. They can build briefings only if you check the box below; briefings count toward your plan limit. Only connect assistants you trust.

The screen rows are: App, Return URL, Sign-in scopes. The footer reads: Weather decision support only. You are pilot in command. PlaneWX never tells you to go or not to go. The buttons are Allow and Deny.

  • Permission read. Always granted when you choose Allow. Lets the assistant read your profile, aircraft, personal minimums, saved trips, stored briefings, Self Debriefs and FRATs, look up airports, read your limits, and send PlaneWX a note with report_discrepancy.
  • Permission briefings. Granted when you check "Also allow building briefings". Lets the assistant build new briefings with score_trip and find_departure_windows, save a candidate as a trip, and change a saved trip with update_trip. Each new briefing uses a scoring run from your daily limit.

Tools your assistant can call

Each line gives the tool name, what it does, the inputs it takes and what it returns. Tools marked briefings need the briefings permission. The others need only the read permission.

  • resolve_airport: Finds an airport from a name, city, City ST, ICAO or FAA id. Inputs: query, and limit (1 to 10, default 5). Returns: Matching airports with both icao and faa_id, and needs_choice when more than one airport could be meant.
  • get_pilot_profile: Reads your PlaneWX profile. Inputs: None. Returns: Plan, home airport, default aircraft, aircraft with tail number, type and effective minimums, personal VFR and IFR minimums, and today's connector briefing usage. It does not score anything.
  • get_my_limits: Reads your limits from the same counters that enforce them. Inputs: None. Returns: Plan and trial status, daily scoring runs used and left with the local reset time, candidates per leg, the 10-minute burst limit, the read rate limit, the weekly refresh limit, and your plan's saved trip limit and monitored trip limit. It does not spend a scoring run.
  • list_trips: Lists your saved trips. Inputs: status (upcoming by default, past or all), from, to, cursor, limit (default 10, 1 to 25, or 1 to 5 with include_details), include_past_hours (0 to 24), include_details, include_frat_history, and max_briefed_score (0 to 100, past trips only). Returns: Per trip: trip_id, route, aircraft, ETD, flight rules, the stored WX Score and band from the latest briefing, when it was briefed, whether it is monitored, and a link. Nothing is re-scored and it does not count toward the daily scoring limit.
  • get_trip_briefing: Reads the stored briefing for one of your saved trips. Inputs: trip_id, and optional part, cursor and include_frat_history. Returns: The stored WX Score and band, score breakdown, cautions, pre-flight checks, terminal weather, en-route hazards, a NOTAM summary and the trip's FRATs. It never re-scores and never fetches new weather.
  • score_trip (briefings): Runs one full briefing for a route and departure time without saving a trip. Inputs: origin, destination and departure_local, and optional aircraft_id, flight_rules (VFR or IFR), cruise_altitude_ft, constraints, route and compare_trip_id. Returns: The WX Score and band, data_confidence, top reasons, the checks that ran, ETD, ETE and ETA, sunrise and sunset, and a link to the full briefing. It uses 1 scoring run.
  • find_departure_windows (briefings): Scores a few candidate departure times for a route without saving trips. Inputs: origin, destination and out_day, and optional out_earliest (default 07:00), out_latest (default 17:00), return_day, return_earliest, return_latest, allowed_ranges, options_per_leg (default 3), aircraft_id, flight_rules, cruise_altitude_ft and constraints. Returns: Up to 3 candidate times per leg and 6 per ask, ranked best first, each with its WX Score, band, ETD, ETA, sunrise and sunset, and a link. Each scored window uses 1 scoring run.
  • get_window_results: Reads the stored results of an earlier find_departure_windows ask. Inputs: ask_id. Returns: The same fields as find_departure_windows. It does not start new briefings and does not count toward the daily scoring limit.
  • save_candidate_as_trip (briefings): Saves a scored candidate as a normal PlaneWX trip. Inputs: candidate_id. Returns: The saved trip. It copies the route, departure time, aircraft, cruise altitude and flight rules, not the score, and the new trip gets its own fresh briefing. Saving the same candidate again returns the same trip. Your plan's saved-trip limits apply.
  • update_trip (briefings): Changes the route, ETD or cruise altitude of a saved trip in two steps, preview then confirm. Inputs: trip_id, and optional route, waypoints (not accepted with route), etd, cruise_altitude_ft, confirm and preview_token. Returns: A preview with the saved and new values and a preview_token, or after confirm, the saved trip. The steps and costs are listed in the update_trip section below.
  • report_discrepancy: Sends PlaneWX a note when something in a result looks wrong. Inputs: note (up to 500 characters), and optional candidate_id and trip_id. Returns: A confirmation that the note was recorded for PlaneWX review. Only your user id and the note are logged. It does not change scores or limits.

Edit a saved trip with update_trip

  • update_trip changes the route, ETD or cruise altitude of one saved trip. It needs the briefings permission.
  • Step 1, preview: the assistant sends the change without confirm. PlaneWX returns the saved and new values, the resolved waypoints, notes and a preview_token. The preview saves nothing and uses no scoring run.
  • Step 2, confirm: the assistant sends confirm true with the same trip_id, the same change and the preview_token. The token is valid for 10 minutes. PlaneWX runs one new score and saves the change and the new briefing together.
  • A route change, an altitude change, a new date, or an ETD move of more than 30 minutes builds a new briefing and uses 1 scoring run.
  • An ETD move of 30 minutes or less on the same date is saved without a new briefing and uses 0 scoring runs.
  • If the new briefing cannot be built, nothing is saved and the scoring run is returned.
  • A new briefing reaches 14 days ahead, the same as the forecast reach for a WX Score. For a departure more than 14 days away, a change that needs a new briefing is not saved and uses no scoring run.
  • ETD: it must include a time zone, such as Z or an offset. An ETD without a zone is refused. A past ETD is refused. An ETD more than 400 days ahead is refused, in the preview and at confirm. An ETD exactly 400 days ahead is accepted.
  • Cruise altitude: a whole number of feet from 1000 to 60000.
  • Route: send route as text, or DCT to reset to direct. route and waypoints together are refused.
  • A trip that departs in under 10 minutes, or has already departed, cannot be updated.
  • ETA and fuel are not accepted.

score_trip accepts an optional route string. Airways (V/J/T/Q) are dropped with a note. A SID/STAR whose name starts with a fix (for example SADDE6) is scored at that fix (SADDE) with a note, the same way the app scores filed routes; a procedure whose base is not a fix is left out with a note. A navaid radial (for example LAX090 or PRB300020) is scored at its navaid with a note. A place-bearing-distance token (for example PRB/090/020) is scored at its place id with a note. A latitude/longitude token is scored as a point and is refused when it does not fit the origin-to-destination route. When the app's procedure-skip mode is live, procedures and radials are left out with a note. Unknown fixes are refused, and the resolved waypoint path is scored. save_candidate_as_trip writes a trip after the pilot confirms.

Daily limits

This is a Pro Plus Labs feature. Turn it on under Profile, Preferences, PlaneWX Labs. It is not available on Free, Casual, or Pro without a Pro Plus trial. See Plans for how this sits next to other plan limits.

  • Scoring runs: trial 12/day and Pro Plus 60/day, resetting at local midnight in your home time zone.
  • Candidates per search: up to 3 per leg (up to 6 per ask for a round trip).
  • Burst limit: 30 scoring starts per 10 minutes.
  • Read-tool rate limit: 30 read calls per minute.

Ask your assistant "What are my limits?" to see your real usage and remaining for today (daily scoring used and left, local reset time, burst and read rates, weekly refresh, and the trial pool when on trial). Your assistant reads these from get_my_limits.

Save a candidate as a trip

After score_trip or find_departure_windows returns a candidate, you can save it two ways. In chat, ask the assistant to call save_candidate_as_trip (needs the briefings permission). In the app, open the candidate briefing link and use the Save as trip button. Both copy route, departure time, aircraft, cruise altitude, and flight rules. They do not copy the candidate WX Score. The new trip gets its own fresh briefing under the same rules and schedule as a trip you create in the app. After a successful save, the candidate page shows Saved as trip. with an Open trip link.

On the candidate briefing page, tap Save as trip. When it finishes, the button is replaced by Saved as trip. and an Open trip link to the new trip briefing.

Example prompts

  • What are my limits?
  • What upcoming trips do I have?
  • Show my FRATs where I chose no-go this year.
  • Am I current for a passenger flight Saturday, and what is a good time to go to 8V2? Check currency in ForeFlight, then use PlaneWX find_departure_windows for weather.
  • Find the best time Saturday for KGDJ to 8V2 in PlaneWX, then create the flight in ForeFlight with those times.
  • Compare the ForeFlight briefing with PlaneWX for my KGDJ to 8V2 flight and list where they disagree.

Watch example: "Keep an eye on my KGDJ to 8V2 briefing; if it drops below 50% or icing becomes a problem, find me a later time today."

That watch request needs refresh and watch tools that are not in PlaneWX MCP yet. The assistant can list saved trips with list_trips and read a stored briefing with get_trip_briefing, but it cannot watch a trip on its own today. Save the candidate as a trip in PlaneWX (save_candidate_as_trip or the in-app Save as trip button) and check the briefing there, or ask again later with score_trip or find_departure_windows.

Example: October hours with ForeFlight and PlaneWX

Pro Plus only.

PlaneWX supplies the scheduled trips and briefing times. ForeFlight is a separate connector the pilot adds in Claude. The pilot in command still makes every go or no-go decision.

Claude answering an October flight hours question using a ForeFlight logbook connector and PlaneWX scheduled trips
"Using my ForeFlight logbook, how many hours have I flown so far in October? Count only approved entries and ignore drafts. Then, using PlaneWX, how many flight hours do I have scheduled for the rest of October? Give me the total for the month."

See it in action

Two short demos of the PlaneWX connector in Claude.

Use it with other aviation apps

You can connect PlaneWX and ForeFlight, or other aviation apps, in the same chat. Ask the assistant to check your logbook in the other app and then find PlaneWX windows that fit, for example arriving before sunset. PlaneWX does not read your logbook or medical, and it does not check currency.

If a feature does not work

If a feature does not seem to work, disconnect and reconnect to the PlaneWX connector. In PlaneWX, open your Profile, then the Account tab, then Connected apps, and choose Disconnect next to the assistant. You can also revoke the PlaneWX connection in your AI assistant's app or connector settings. Then follow the steps for your assistant above to connect again.

How to disconnect

To disconnect, revoke the PlaneWX connection in your AI assistant's app or connector settings. Sign Out of All Devices (PlaneWX Settings) and changing your password also disconnect every assistant. The regular Sign Out only signs out the device you are on. After revoke, tools stop until you connect again.