developer_board MCP for exact-date flight comparison agents

Skiplagged Flights MCP

Search exact Skiplagged itineraries from AI apps with one structured MCP call, then hand booking-ready deep links back to the user.

  • check_circle Exact-date one-way and roundtrip searches in a single tool call
  • check_circle Airline, stops, timing, duration, and layover filters
  • check_circle Booking-ready deep links plus widget-friendly result cards
sk_flights_search sk_resolve_iata

Typical MCP flow

  1. 1. Resolve city names only when needed

    Use sk_resolve_iata only to turn a plain city name like New York or London into a valid IATA location code.

  2. 2. Search the complete itinerary in one shot

    Send both outbound and return dates in the same sk_flights_search call and let Skiplagged return ranked itineraries plus booking links.

Tools

The public MCP surface is lean: one resolver for city names, and one main search tool for exact-date flight itineraries.

Tool

sk_flights_search

flight

Use this tool for exact fixed-date flight searches between explicit origin and destination airports or resolved IATA location codes. It supports roundtrip searches, fare class, passenger counts, airline preferences, stop filters, and timing constraints.

Required inputs

  • origin
  • destination
  • departureDate

Optional filters

  • returnDate
  • maxStops
  • preferredAirlines
  • maxFlightDuration

Returns

  • Ranked itinerary results
  • Widget-ready cards
  • Booking deep links

Tool

sk_resolve_iata

pin_drop

Use this helper only when the user gives a plain city name and you need a valid IATA location code before calling the search tool.

Required input

  • input city name only

Examples

  • New York
  • London
  • Tokyo

Returns

  • Resolved IATA location code
  • Cleaner tool inputs for exact search

Response JSON

The most valuable output is not just raw search rows. The MCP also returns normalized cards with route labels, date labels, price display strings, and booking links that are ready for downstream UI or agent reasoning.

{
  "search": {
    "route_label": "SEA to CCU",
    "date_label": "May 1 - May 22 • Return",
    "trip_type": "round_trip",
    "flight_class": "economy"
  },
  "count": 5,
  "cards": [
    {
      "route_label": "SEA to CCU",
      "price_display": "$1195",
      "booking_url": "https://skiplagged.com/...",
      "outbound": {
        "airline": "Qatar Airways",
        "from_airport": "SEA",
        "to_airport": "CCU",
        "departure_time": "4:30 PM",
        "arrival_time": "2:30 AM",
        "duration": "21h 30m",
        "stops_label": "1 stop",
        "stop_detail": "DOH"
      }
    }
  ],
  "results": [ ... ]
}

Quickstart

A typical integration resolves city names only when the user did not provide explicit airport codes, then calls the main search tool once with the full itinerary.

Step 1

Resolve city names if needed

{
  "tool": "sk_resolve_iata",
  "arguments": {
    "input": "New York"
  }
}

Step 2

Search the complete itinerary

{
  "tool": "sk_flights_search",
  "arguments": {
    "origin": "NYC",
    "destination": "LON",
    "departureDate": "2026-05-01",
    "returnDate": "2026-05-22",
    "fareClass": "economy",
    "maxStops": "one",
    "preferredAirlines": ["DL", "UA"]
  }
}

Access

Hosted MCP endpoint with custom flight UX

This MCP is surfaced through Infoseek’s hosted Skiplagged app endpoint. The search tool is paired with a custom results widget so exact itineraries can render directly inside chat surfaces and AI agent workflows.

Why These Outputs Matter

Skiplagged is most useful when you need both structured filtering and booking-ready results. The output is already shaped for comparison UIs, not just backend logging.

price_check

Comparable prices

Price display values arrive normalized for ranking and side-by-side comparisons across providers.

tune

Rich search controls

Stops, airline preferences, timing, and duration constraints can stay inside one exact-date search call.

link

Booking handoff

Each itinerary includes deep links so the user can move directly from comparison to booking.

Use Cases

This MCP is a fit for travel agents and copilots that need exact itineraries, not broad discovery pages.

Flight-shopping agents

Compare concrete itineraries on specific dates and pass booking links back to the user immediately.

Travel planning copilots

Keep exact return trips in one tool call instead of stitching outbound and inbound searches together.

Provider-comparison workflows

Use the widget-ready card payload to rank and display Skiplagged alongside other flight sources.