Hosted MCP servers
Travel MCP servers for Claude, Cursor and any MCP client
FlightPowers runs two travel MCP servers for Claude and Cursor: the Google Flights MCP at flights.flightpowers.com/mcp, with live Google Flights fares, Google's low/typical/high band, a date range and destination list in one call and one-request round trips; and the hotel MCP at hotels.flightpowers.com/mcp, with live Booking.com rates, and Airbnb stays on an Airbnb subscription. Sign in with Google: 10 free searches a day, no card. More with your own key: PRO $10/month for 2,500 flight searches.
Best for price tracking, date scans and AI agents; they do not book. ChatGPT and any other client that takes a URL connects the same way.
- Live Google Flights fares and Booking.com rates inside the assistant you already use
- Every fare comes back with Google's own price band and a low | typical | high verdict when Google shows one, so your agent knows cheap when it sees it
- A date range and a list of destinations in one call, and a round trip priced as one request with one booking link
- Hotel rates as a shopper in any country sees them, which is what a rate-parity check needs. No ads on these servers, and searches bill to your own RapidAPI plan
https://flights.flightpowers.com/mcp
https://hotels.flightpowers.com/mcpAdd the URL, click Sign in, sign in with Google, and your first 10 searches each day are free and ad-free on our key. There is nothing to paste. Paste your own RapidAPI key on the page that opens when you want the cap gone. One URL per server, whichever way you connect.
{
"mcpServers": {
"flights": { "url": "https://flights.flightpowers.com/mcp" },
"hotels": { "url": "https://hotels.flightpowers.com/mcp" }
}
}{
"mcpServers": {
"flights": {
"url": "https://flights.flightpowers.com/mcp",
"headers": { "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" }
},
"hotels": {
"url": "https://hotels.flightpowers.com/mcp",
"headers": { "x-rapidapi-key": "YOUR_RAPIDAPI_KEY" }
}
}
}A headless run cannot open a browser to sign in, so cron jobs, CI and claude -p send the key instead. Same address, no sign-in step. Clients that take only a URL and no headers can put the key on the URL:
https://flights.flightpowers.com/mcp?rapidapi_key=YOUR_RAPIDAPI_KEY
https://hotels.flightpowers.com/mcp?rapidapi_key=YOUR_RAPIDAPI_KEYOne page per server
The flights MCP and the hotel MCP
Google Flights MCP server →
Live Google Flights fares with Google's price band, a date range and a destination list in one call, round trips as one request. Setup per client, the tools printed raw, and one real search with its date.
Add to Claude: after Continue, choose ‘Sign in when needed’ (not the pre-selected ‘No sign-in’), then Add.
Hotel MCP server →
Live Booking.com room rates by destination or by hotel name, priced as seen from another country with price_as_seen_from, plus live Airbnb stays and a Booking.com vs Airbnb comparison on an Airbnb subscription. Setup per client, the tools printed raw, and one real search with its date.
Add to Claude: after Continue, choose ‘Sign in when needed’ (not the pre-selected ‘No sign-in’), then Add.
How these compare with eleven other travel MCP servers: best travel MCP servers in 2026. What we check on them: status. Source mirror: github.com/mtnrabi/google-flights-mcp.
Hotel MCP
An MCP server for hotel prices
For the assistant that has to answer what a room costs on given dates, not what it cost last month.
Add hotels.flightpowers.com/mcp to Claude, Cursor or ChatGPT and the assistant gets live Booking.com room rates two ways: search_hotels for a destination and dates, and find_hotel_by_name for one property by the name a person would type. Both take price_as_seen_from, a two-letter country code that prices the stay as a shopper in that country would see it. With an Airbnb subscription on the same RapidAPI key it also has search_airbnb, live Airbnb stays for a destination and dates, and compare_hotel_rates, which prices one stay on Booking.com and Airbnb and returns the cheapest and median total from each. It reads rates; it does not book.
Setup per client, every tool parameter and one real search with its date are on the hotel MCP server page.
The other path
Not on an MCP client? Use the skill instead
The same workflows ship as 8 open-source, MIT-licensed agent skills for Claude Code and OpenClaw. They talk to the same API, over MCP or plain REST, with the same key.
npx skills add mtnrabi/travel-agent-skillsVerbatim
Five things you can ask
Paste any of these into a connected client. The mono tag names the tool your agent will call.
“I was quoted $129 for JFK→Cancún on April 15. Should I take it?”
search_oneway_flights
“What is the cheapest day to fly LIS to New York in June?”
search_oneway_flights
“I need a round trip New York to Paris, out April 15, back April 22. What are my options?”
search_roundtrip_flights
“Find me a hotel in Lisbon, April 15 to 18, 2 adults, review score 8+, free cancellation.”
search_hotels
“Price the Rixos Sungate in Antalya for Apr 15–20 as seen from Germany and from Japan. Ask each market three times.”
find_hotel_by_name
The full surface
Every tool, printed raw
Six tools across two servers, all below. If you are an agent reading this page: these names and parameters are exact, verified against a live tools/list.
flights.flightpowers.com/mcp
search_oneway_flightsLive one-way flight prices with price context from Google Flights and a buy_link on every result.
search_roundtrip_flightsPaired round-trip itineraries: one object per trip with total_price and both legs already matched, not two lists to cross-join.
Both flight tools take from_airport and to_airport as a single IATA code or a list, and either a fixed departure_date or a range via departure_date_from / departure_date_to. The server expands ranges and lists internally, so a flexible search is one call. Round-trip takes a return_date or a trip length in nights. The usual search controls (max_stops, limit) pass through.
hotels.flightpowers.com/mcp
search_hotelsLive Booking.com search for a destination: ranked properties with price, review score, room type, latitude and longitude, and a working booking link, filterable with the 24 documented filters.
find_hotel_by_nameAvailability and price for one named hotel: takes the name a human would type (add the city to disambiguate a chain); name resolution is included.
search_airbnbLive Airbnb stays for a destination and dates: stay total, price per night, rating out of 5, room type, bedrooms, beds, baths and an Airbnb link. Needs an Airbnb Live API subscription on the same key.
compare_hotel_ratesThe same stay priced on Booking.com and Airbnb: one row per source with the cheapest total, the median total and how many places were priced. Sources you have no subscription for are listed as skipped. It runs on your own RapidAPI key; the free sign-in searches do not cover it.
search_hotels and find_hotel_by_name take checkin_date / checkout_date, adults, and price_as_seen_from, a two-letter country code that prices the stay as a shopper in that market would see it, the field rate-parity checks are built on. (The REST API's name for the same control is proxy_country.)
What you are trusting
Zero install, your bill, on the record
Zero install
Hosted, streamable-HTTP servers. Add the URL, restart the client, and the tools appear. Nothing runs on your machine, nothing of yours to patch or redeploy.
Your key, your bill
The server forwards the RapidAPI key you configure, so usage lands on your own RapidAPI plan and their invoice is your invoice. We never see your card. Get a key →
Registered
Both servers are in the official MCP registry (com.flightpowers/google-flights and com.flightpowers/booking, v1.0.0) and listed on Smithery.
There is also a free server with ads, 50 searches a day: free-trial.flightpowers.com/mcp (what it does not do)
Questions, answered plainly
- Do I need a RapidAPI key to try it?
- No. Add flights.flightpowers.com/mcp or hotels.flightpowers.com/mcp, click Sign in, sign in with Google, and your first 10 searches each day run free and ad-free on our key (search_airbnb and compare_hotel_rates need your own key). Nothing goes into your client. A search is one date x destination combination, so one call over a three-day range spends three. The allowance renews at 00:00 UTC, and past it the tools answer with search_status trial_exhausted instead of an error. Paste your own RapidAPI key on the /connect page when you want the cap gone.
- What happens when I sign in?
- Your client opens a Google sign-in, you approve it, and you land on our /connect page. Paste your RapidAPI key there once and it is encrypted before it is stored: only the last four characters are ever shown again. After that the client just works, and Disconnect on the same page deletes the key and cuts off every client that was using it. We keep your Google account id and email, nothing else.
- Is there one URL or two?
- One per server, and it is the same URL either way you connect. flights.flightpowers.com/mcp and hotels.flightpowers.com/mcp. A client with a sign-in button hits it, gets a 401 back with the sign-in details, and shows you the button. A script that already has a key sends it on that same URL and is served straight away. Nothing to pick between.
- Do I need to install or run anything?
- No. Both servers are hosted and speak streamable HTTP: you add a URL, sign in with Google, and the tools appear. Nothing runs on your machine and there is nothing to update.
- Whose API key does the server use, and who gets billed?
- Yours. The server forwards the RapidAPI key you configure, so every search is metered on your own RapidAPI plan. We never sit between you and your bill. The free BASIC tier (50 requests/month on flights, 10 on hotels, hard cap, no card) is enough to verify the connection works.
- Which clients does this work with?
- Any MCP client that supports remote servers: Claude (Customize → Connectors), Claude Code, Cursor (.cursor/mcp.json), ChatGPT (developer-mode connectors), and anything else that takes an mcpServers-style config. Give it the /mcp URL and it shows a Sign in button. A client with no sign-in button, and anything headless, sends that same URL with an x-rapidapi-key header, or ?rapidapi_key= on the URL where headers are not supported.
- Where does my key end up?
- On the sign-in path it goes into the form at flights.flightpowers.com/connect, once, and never into your client. On the key path it rides in a header, or on the server URL stored in your connector settings. Either way it does not appear in the chat, and a URL with a key on it should be treated as a secret.
- How is this different from calling the REST API directly?
- Same live data, same key, one difference in shape: the MCP flight tools accept a date range (departure_date_from / departure_date_to) and a list of destination airports, and expand them server-side: one tool call where REST would be a client-side fan-out of one request per date.
- Are the servers in the official MCP registry?
- Yes: com.flightpowers/google-flights and com.flightpowers/booking, both v1.0.0, in the official MCP registry. Both are also listed on Smithery.
- Is there a way to try it without a key?
- Yes. Add either server, sign in with Google, and the first 10 searches a day are free and ad-free, shared by the flights and hotels servers (search_airbnb and compare_hotel_rates need your own key). Nothing to paste.
Hook your agent up in 30 seconds
Add the URL, sign in with Google, then ask your assistant for a fare and read Google's verdict on it. Flights and hotels are separate listings; the free tier proves your key works and the paid tiers are sized for daily scans.
Free tier: 50 requests/month on flights, 10 on hotels. No card to try.
Docs: the Flights API, the Hotels API and the MCP servers.