Live flight status and flight webhooks as tools for your AI assistant. Add FlightByte to Claude in one click, or connect Claude Code, Cursor, VS Code and any MCP client.

The FlightByte MCP server gives an assistant the API as tools. Ask it whether a flight is on time and it looks the flight up. Ask it to watch one and it creates the subscription. Tell it your webhook stopped firing and it reads the delivery log. While it writes your integration, it searches these docs instead of guessing.

Add to Claude Add to Cursor Install in VS Code

Serverhttps://mcp.flightbyte.dev/mcp

Localnpx -y @flightbyte/mcp

Listed in Claude’s connector directory. The docs tools work without signing in; Claude asks you to sign in to FlightByte the first time it needs your account.

What you can ask

You ask	What happens
"Is TK1848 on time today? Which gate?"	`get_flight` returns the live snapshot: phase, gate, terminal, delay, and the best known departure and arrival times.
"TK1 from Istanbul tomorrow: when does it leave?"	TK1 flies two legs that day. The assistant passes `origin: "IST"` and gets the right one instead of a guess.
"Watch PC1001 on Friday and post every change to https://api.example.com/hooks/flights."	`create_subscription` starts the watch and hands you the signing secret, shown once.
"Our webhook stopped firing. Why?"	`get_subscription` and `list_deliveries` show the status, and the HTTP code and error of every recent attempt.
"Add a FlightByte webhook receiver with signature verification to this Express app."	`search_docs` and `get_doc_page` pull the exact steps from these docs, so the code matches the API.

Connect

The server runs in two places. The hosted server at https://mcp.flightbyte.dev/mcp needs nothing installed: Claude signs in to your FlightByte account with OAuth, and other clients send your API key. The local server, npx -y @flightbyte/mcp, runs on your machine with Node.js 20 or later and reads the key from FLIGHTBYTE_KEY.

FlightByte is in Claude's connector directory, on claude.ai, Claude Desktop and the mobile apps.

Open FlightByte in the directory and add it.
Ask about a flight. The docs tools work straight away; the first time Claude needs your account, it shows a Connect button.
Sign in to FlightByte and allow access. The call goes through, and from then on every tool works with your account and your plan.

There is no key to copy. To see or end Claude's access, open Connected apps in your dashboard.

On Team and Enterprise plans, an Owner adds the connector for the organisation first, under Organization settings → Connectors; each member then signs in with their own FlightByte account.

To add it by address instead, use Customize → Connectors → Add custom connector with the URL https://mcp.flightbyte.dev/mcp, and leave the OAuth fields empty.

Signing in

The server reaches the API as you, in one of two ways:

OAuth, in Claude. You sign in to FlightByte and allow access once; Claude never sees an API key. Every app you allowed is listed under Connected apps, where you can revoke it.
An API key, everywhere else: in a header for the hosted server, or in FLIGHTBYTE_KEY for the local one. The hosted server uses the key for that request only and never stores or logs it. Create and rotate keys under API keys.

Without either, search_docs and get_doc_page still work, so an assistant can read the documentation before you have an account. Any other tool asks you to sign in or add a key. Sign-up is free and needs no card.

Tools

Docs. No key or sign-in needed.

Tool	What it does
`search_docs`	Keyword search over the docs, the API reference, the guides and the glossary. Returns titles, links and snippets.
`get_doc_page`	Any docs page as Markdown, from a link or a path such as `/docs/webhooks`.

Flights. Read-only.

Tool	What it does	API
`get_flight`	Live status of one leg: phase, gates, terminals, baggage belt, scheduled, estimated and actual times, delay, aircraft, codeshares, and every leg the number flies that day.	Get a flight
`search_flights`	The same lookup with query parameters.	Search flights
`get_flight_timeline`	The airline's own change history for a leg, newest first.	Flight timeline

Subscriptions.

Tool	What it does	Access
`create_subscription`	Watch a flight and receive a signed webhook for every change. Counts as a watched flight on your plan.	writes
`list_subscriptions`	Your subscriptions, filtered by status, carrier, number or date.	read-only
`get_subscription`	One subscription, with its status and delivery counters.	read-only
`update_subscription`	Change the webhook URL, event filter, delay threshold, headers or metadata.	writes
`pause_subscription`	Stop polling and deliveries without losing anything.	writes
`resume_subscription`	Resume a paused or automatically suspended subscription.	writes
`delete_subscription`	Delete a subscription for good.	destructive
`send_test_event`	Send a signed test webhook to the subscription's URL.	writes
`list_deliveries`	Recent delivery attempts, with HTTP status and errors.	read-only
`list_events`	Recent events, with the exact payloads that were sent.	read-only

Parameters carry the API's own names (carrier, flightNumber, date, origin, webhookUrl and so on), and results are the API's JSON. The API reference describes every field.

Your plan and your data

The same plan, the same limits. Each tool that calls the API is one request on your plan, and shows up in your dashboard's request log like any other. create_subscription uses one of your plan's watched flights.
Signing secrets stay out of the chat. No tool reveals or rotates a webhook signing secret, because either would put it into the conversation. create_subscription returns the secret once, as the API does, and tells the assistant to hand it to you. To see it again or replace it, use Reveal the secret or Rotate the secret.
Clients know what is safe. Read-only tools are marked read-only and delete_subscription is marked destructive, so your client can ask before it runs. The assistant is told that create_subscription creates a billable watched flight and should only run when you ask for one.
Docs fetches stay here. get_doc_page only reads pages from flightbyte.dev.

When something goes wrong

The server answers errors with what to do next, and the assistant usually handles them on its own.

You see	What it means
"No FlightByte API key is configured"	The client has neither a key nor a sign-in. In Claude, ask about a flight again and choose Connect; elsewhere, add your key as shown above.
A list of `legs`	The flight number flies more than one leg that day. Say which airport it leaves from, and the assistant passes `origin`.
`402` with `watched_flight_limit`	Your plan's watched flights for this month are used up. They reset on the 1st (UTC), or you can change your plan.
`429`	Too many requests in a short time. The assistant is told how long to wait.

Source and packages

The server is open source under the MIT license, at github.com/flightbyte-dev/flightbyte-mcp. The local server is @flightbyte/mcp on npm.

Writing an integration rather than chatting with the API? Build with AI has a prompt, rules files for your repository and a Claude Code skill.

MCP server