Skip to content

Hosted MCP servers

Connect Google Flights & Booking.com to any MCP client

Ask your assistant what a flight costs and get today's real fare, with Google's own price band next to it. Add one URL, sign in with Google, and Claude, Cursor or ChatGPT can search live flights and hotels for you. Nothing to install.

  • 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, 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
Free tier: 10 requests/month, no credit card
Setup: one URL per server, then sign in with Google
add this URL · flights and hotels
https://flights.flightpowers.com/mcp
https://hotels.flightpowers.com/mcp

Add the URL, click Sign in, sign in with Google, and paste your RapidAPI key once on the page that opens. Nothing else goes into your client. One URL per server, whichever way you connect.

same thing in an mcp.json client
{
  "mcpServers": {
    "flights": { "url": "https://flights.flightpowers.com/mcp" },
    "hotels": { "url": "https://hotels.flightpowers.com/mcp" }
  }
}
same URL, key in a header · scripts, CI, clients without a sign-in button
{
  "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:

key on the URL
https://flights.flightpowers.com/mcp?rapidapi_key=YOUR_RAPIDAPI_KEY
https://hotels.flightpowers.com/mcp?rapidapi_key=YOUR_RAPIDAPI_KEY

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.

terminal
npx skills add mtnrabi/travel-agent-skills
The 8 skills →

Verbatim

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 January 1. Should I take it?

search_oneway_flights

What is the cheapest day to fly LIS to New York in November?

search_oneway_flights

I need a round trip New York to Paris, out October 6, back October 13. What are my options?

search_roundtrip_flights

Find me a hotel in Lisbon, October 9 to 12, 2 adults, review score 8+, free cancellation.

search_hotels

Price the Rixos Sungate in Antalya for Oct 5–10 as seen from Germany and from Japan. Ask each market three times.

find_hotel_by_name

The full surface

Every tool, printed raw

Four tools across two servers. 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_flights

Live one-way flight prices with price context from Google Flights and a buy_link on every result.

search_roundtrip_flights

Paired 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_hotels

Live Booking.com search for a destination: ranked properties with price, review score, room type, and a working booking link, filterable with the 24 documented filters.

find_hotel_by_name

Availability and price for one named hotel: takes the name a human would type (add the city to disambiguate a chain); name resolution is included.

Hotel tools 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.

Separate, and honestly labelled

A free, ad-supported server also exists

free-trial.flightpowers.com/mcp serves all four tools, flights and hotels, with no RapidAPI key at all. Add the URL, sign in with Google, and you are searching: 50 searches a day and 250 a month under your own name. The trade: every result carries one labelled sponsored card, and one call searches at most 15 date × destination combinations instead of 30. Use it to try the tools before getting a key; point production and anything you ship at the keyed servers above.

Connect it, and read the full list of what it does not do →

Questions, answered plainly

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 (10 requests/month, 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 (Settings → 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: a separate free, ad-supported server. Sign in with Google and you get the same four tools with no RapidAPI key at all, 50 searches a day and 250 a month under your own name. Every result carries one labelled sponsored card and one call searches at most 15 date × destination combinations instead of 30. Connect it from the free tools page. It is for trying the tools before you get a key, not for production.
no card to tryBYO key, billed to your own planworks with any MCP client

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: 10 requests/month. No card to try.