Model Context Protocol (MCP)

Connect ALLFLYGHTS to AI assistants and automated travel workflows via MCP. Read-only flight route discovery.

Approval required

MCP access is approval-based. Apply via the developer portal — we review based on use case, expected volume, and alignment with read-only flight search.

Endpoint

The MCP server lives at:

https://mcp.allflyghts.com/mcp

Configure your MCP client to connect over the standard protocol; ALLFLYGHTS exposes typed tools for location lookup and route search.

Authentication

Authenticate every request with a bearer token issued from your portal dashboard:

Authorization: Bearer <MCP_TOKEN>

Tokens are scoped to your organisation and shown once at creation time. Lost a token? Rotate it — the previous secret is invalidated immediately.

Use cases

AI travel assistants

Chat agents that turn natural-language travel intent into structured route options without bespoke airline integrations.

Automated booking orchestration

Workflow tools that surface candidate routes for human review or downstream booking systems.

Geo-aware suggestions

Assistants that handle 'fly to Cambridge' (which one?) without dictating an airport up front.

Multi-leg planning

Multi-city and open-jaw itineraries built from independently-resolved cities or fixed airports.

Quotas

Quotas are issued at approval time and reflect tier and expected volume. AI Access launches with sensible defaults (rate limits per second / per day); MCP Partners get fair-use caps.

When a request exceeds your quota the server responds with 429 Too Many Requests. Back off and retry, or contact us to discuss a higher tier.

Read the public docs: Overview · REST API · full reference (REST · MCP) · OpenAPI spec (REST · MCP) · MCP server.json.