Google Hotels MCP
ai.wondel/google-hotelsVersion 1.0.0Live Google Hotels search: properties with rates and ratings, plus photos and reviews.
Status
Responds307 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:45 UTC
- Latency
- 307 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.wondel.ai/google-hotels/mcpResponds307 msNo sign-in
Claude Code
claude mcp add --transport http google-hotels https://mcp.wondel.ai/google-hotels/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: google-hotels
Remote MCP server URL: https://mcp.wondel.ai/google-hotels/mcpCursor
{
"mcpServers": {
"google-hotels": {
"url": "https://mcp.wondel.ai/google-hotels/mcp"
}
}
}VS Code
code --add-mcp '{"name":"google-hotels","type":"http","url":"https://mcp.wondel.ai/google-hotels/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
google_hotels_photosFetch the full set of photos for a single Google Hotels property via SerpAPI. Requires a `property_token` taken from a google_hotels_search result. Paginate with next_page_token. | Not declared | Not declared | Not declared | Not declared |
google_hotels_reviewsFetch reviews for a single Google Hotels property via SerpAPI. Requires a `property_token` taken from a google_hotels_search result. Filter by category_token or source_number, order with sort_by, and paginate with next_page_token. | Not declared | Not declared | Not declared | Not declared |
google_hotels_searchSearch Google Hotels live via SerpAPI. Returns properties (hotels and, with vacation_rentals, rentals) with names, prices/rates, overall ratings, review counts, amenities, images and location, plus the brands/property_types/amenities filter ids you can feed back in. Requires q (a destination, area or hotel name), check_in_date and check_out_date (YYYY-MM-DD). Every property in the results carries a `property_token`: pass it back here (keeping the same check_in_date/check_out_date) to get that one property's full details, or hand it to google_hotels_photos and google_hotels_reviews. Paginate with next_page_token. Prices are in `currency` (default USD). Result shape: { source, fetchedAt, query, search_metadata, search_parameters, search_information, brands, ads, properties: [...], serpapi_pagination } — the list key is `properties` (ads are separate). Each property: { type, name, property_token, link, gps_coordinates, rate_per_night: { lowest, extracted_lowest }, total_rate, prices: [{ source, num_guests, rate_per_night }], overall_rating, reviews, hotel_class (label), extracted_hotel_class (number), amenities, images: [{ thumbnail, original_image }], nearby_places, description }. With property_token the single property's fields come back at the top level instead of `properties`. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Repository
- Not given
- Categories (suggested)
- Design and mediaSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared