Skip to content

Add Google Hotels MCP (travel category) - #130

Open
huynhtanan wants to merge 3 commits into
wundercorp:mainfrom
huynhtanan:add-google-hotels
Open

huynhtanan wants to merge 3 commits into
wundercorp:mainfrom
huynhtanan:add-google-hotels

Conversation

@huynhtanan

Copy link
Copy Markdown

Adds one entry (Google Hotels MCP) under a new travel category.

Why a new category

Existing categories (browser-automation, communication, data, design, developer-tools, files, knowledge, observability, orchestration, security) don't fit a travel/hospitality server — hotel pricing isn't dev-tooling or knowledge-base content. Per CONTRIBUTING: "Add a new category only when none of the existing categories fit."

Happy to re-file under data or knowledge if you prefer.

What this server does

  • hotel_entity — property details (amenities, images, OTA ratings, 1 Tripadvisor sample review).
  • hotel_price_calendar — 3-month daily price grid.
  • vacation_rental_search — Google Vacation Rentals results (Airbnb, VRBO, Booking).

Install: uvx --from "git+https://github.com/huynhtanan/google-hotels-mcp.git@v0.1.1" google-hotels-mcp

Only env var: APIFY_TOKEN (free tier works for personal use).

Checklist

  • One MCP server per PR.
  • servers/travel/google-hotels/server.json matches schema (slug, name, category, description, homepage_url, license, status + optional repository_url, package_url, transports, tools).
  • README updated with alphabetically-placed ### Travel section.
  • License MIT.
  • Public, documented repo with v0.1.1 tagged release.

I couldn't run node scripts/validate-catalog.mjs / generate-readme.mjs locally; the JSON matches schema fields and the README row follows the Security section's format exactly. Happy to iterate if the generator produces a different row.

@huynhtanan

Copy link
Copy Markdown
Author

Bumped the pinned release here from v0.1.1 to v0.1.2 in 0d6524b.

v0.1.2 fixes four parameter-name mismatches between the MCP wrapper and the Apify actors that were caught in a CodeRabbit review of a sister PR:

  • maxHotelsPerQuery (not maxResults) → max_results is now actually enforced instead of silently falling back to the actor's 40-item default.
  • hotels (not hotelUrls) → the calendar actor now receives the hotel to price.
  • numberOfDates=90 default → the advertised 3-month calendar actually returns 3 months (actor default was 30 dates).
  • language / country (not Google URL hl / gl) → interface language and country code are honoured end-to-end.

Also flipped include_provider_prices default to false so each paid provider-prices call is explicit opt-in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant