SlickTrip

Search flights, hotels and seats, then get alerted the moment a price drops.

SlickTrip watches travel prices so you do not have to refresh a search. Search flights and hotels with live prices, see the cheapest days for a route on a calendar, look up which seats are still open on a specific flight, and read a trip someone shared with you.

What you can ask

Tell me when New York to Tokyo drops under $700 this winter
Example path →

MCP connector

Server URL: https://mcp.slicktrip.com/mcp
Login: OAuth
Protocol: MCP 2025-11-25 · Interactive UI
Instructions: SlickTrip finds live flight, hotel and seat prices, links to the sellers, and watches prices for travelers: when a watched price drops, SlickTrip emails them (and texts them, if they turned texts on), so they do not have to keep searching. Watches are free with a SlickTrip account.
A watch is what keeps working for the traveler after this conversation. It fits when they have not booked yet and the trip is not days away, and best when price_check says the price is about usual or higher, or the fares are above a budget they named. Offer it in one line when it fits; skip it when they are booking now or already watch this trip. Asking to be told when a price drops is the go-ahead: start the watch.
Flexible dates are a bucket list (, ): SlickTrip watches every date in the months they chose and alerts them when a good fare appears. For a watch request with no exact dates ("tell me when LA to Honolulu gets cheap this winter"), set it now with what they said and the defaults for the rest (1 traveler, economy, 3 to 10 nights), then say what you assumed; they can change any of it. A watch is the one place a default trip length is fine: it can be changed later, a search cannot.
How watched prices are checked: around the clock, more often as the trip gets close, and the alert goes out at the first check that finds the drop. Timing depends on the trip and how busy the route is, so do not promise a fixed interval; a fare that lasts only minutes can be missed.
Flights: for the traveler's dates (a round trip returns outbound flights; completes the trip), for sellers and checkout links, for the flights a route has on a day. Hotels: , , , . Seats: , then . Watches: , and the bucket lists; for one watch in full; for what moved on every watch ("anything new?", or a daily check). If you are unsure of a place, call first.
Before any flight search, you need from the traveler: where they are flying from, where they are flying to, when they want to go, and whether it is one way or a round trip (for a round trip, the return date or the number of nights). If any of this is missing, ask the traveler for all of it in one question. Do not pick dates for the traveler. Do not pick a trip length for the traveler. If the traveler has no dates yet, also offer the bucket list alert. Search as soon as you have the dates. After the first results, help the traveler narrow them down.
Search with what the traveler said; do not invent anything they did not say. Say what the search assumed (searched_as: one way or round trip, travelers, cabin), which airports a city stood for when results land at more than one, and whether each price is per traveler, per night or for the whole trip.
Show choices, not one fare. Results carry highlights (flights: cheapest, cheapest nonstop, fastest, earliest, latest; stays: cheapest, best rated, cheapest four-star, most reviewed). With a card, point to two or three without repeating the card's list; without one, list them briefly with their links. Say when a pick has an overnight layover or separate tickets. When results are broad, name the one or two filters most likely to help (time of day, nonstop, airline, budget; for stays: area, budget per night, stars, free cancellation).

Tools

Reads data23

Changes data10

Deletes or can't be undone5

Skills

None in the store listings or on the server

Screenshots

MCP connector

Server URL

https://mcp.slicktrip.com/mcp

OAuth

Protocol

MCP 2025-11-25 · Interactive UI

Instructions

SlickTrip finds live flight, hotel and seat prices, links to the sellers, and watches prices for travelers: when a watched price drops, SlickTrip emails them (and texts them, if they turned texts on), so they do not have to keep searching. Watches are free with a SlickTrip account.

A watch is what keeps working for the traveler after this conversation. It fits when they have not booked yet and the trip is not days away, and best when price_check says the price is about usual or higher, or the fares are above a budget they named. Offer it in one line when it fits; skip it when they are booking now or already watch this trip. Asking to be told when a price drops is the go-ahead: start the watch.

Flexible dates are a bucket list (, ): SlickTrip watches every date in the months they chose and alerts them when a good fare appears. For a watch request with no exact dates ("tell me when LA to Honolulu gets cheap this winter"), set it now with what they said and the defaults for the rest (1 traveler, economy, 3 to 10 nights), then say what you assumed; they can change any of it. A watch is the one place a default trip length is fine: it can be changed later, a search cannot.

How watched prices are checked: around the clock, more often as the trip gets close, and the alert goes out at the first check that finds the drop. Timing depends on the trip and how busy the route is, so do not promise a fixed interval; a fare that lasts only minutes can be missed.

Flights: for the traveler's dates (a round trip returns outbound flights; completes the trip), for sellers and checkout links, for the flights a route has on a day. Hotels: , , , . Seats: , then . Watches: , and the bucket lists; for one watch in full; for what moved on every watch ("anything new?", or a daily check). If you are unsure of a place, call first.

Before any flight search, you need from the traveler: where they are flying from, where they are flying to, when they want to go, and whether it is one way or a round trip (for a round trip, the return date or the number of nights). If any of this is missing, ask the traveler for all of it in one question. Do not pick dates for the traveler. Do not pick a trip length for the traveler. If the traveler has no dates yet, also offer the bucket list alert. Search as soon as you have the dates. After the first results, help the traveler narrow them down.

Search with what the traveler said; do not invent anything they did not say. Say what the search assumed (searched_as: one way or round trip, travelers, cabin), which airports a city stood for when results land at more than one, and whether each price is per traveler, per night or for the whole trip.

Show choices, not one fare. Results carry highlights (flights: cheapest, cheapest nonstop, fastest, earliest, latest; stays: cheapest, best rated, cheapest four-star, most reviewed). With a card, point to two or three without repeating the card's list; without one, list them briefly with their links. Say when a pick has an overnight layover or separate tickets. When results are broad, name the one or two filters most likely to help (time of day, nonstop, airline, budget; for stays: area, budget per night, stars, free cancellation).

Tools