Native hotel MCP server · cross-OTA rate-shopping · OAuth 2.1
The hotel MCP server that rate-shops every OTA for your agent.
Hotel MCP servers barely exist, and the official hotel APIs are partner-gated. ScoutingAPI’s native server gives an agent seven read-only tools — hotel search, availability, price, and cross-OTA compare with computed min/median — across Booking, Google, and more, behind one OAuth-secured URL.
Add mcp.scoutingapi.com to Claude, Cursor, or n8n · 100 credits free, no card · failed or empty tool calls cost 0 credits
POST https://mcp.scoutingapi.com · tool: search_stays
{
"location": "Sibenik, HR",
"checkIn": "2026-07-13", "checkOut": "2026-07-20",
"adults": 2, "children": 2,
"platforms": ["google", "booking"]
}{
"data": [
{ "id": "stays_google_ChIJN1t_tDeuEmsRUsoyG83frY4", "platform": "google",
"name": "D-Resort Sibenik", "propertyType": "hotel",
"starRating": 4, "guestRating": 4.6, "ratingScale": 5,
"price": { "currency": "EUR", "totalPrice": 2870, "nights": 7 } },
{ "id": "stays_booking_abramovic2", "platform": "booking",
"name": "Apartments Abramovic 2", "propertyType": "apartment",
"starRating": 4, "guestRating": 9.4, "ratingScale": 10,
"price": { "currency": "EUR", "totalPrice": 2122, "nights": 7 } }
],
"meta": {
"platforms": ["google", "booking"], "creditsCharged": 10, "currency": "EUR",
"platformResults": [
{ "platform": "google", "status": "ok", "count": 1 },
{ "platform": "booking", "status": "ok", "count": 1 }
]
}
}Show, don’t sell
Seven read-only tools — hotel search across the OTAs, one schema.
This is an actual search_stays tool result across the hotel OTAs (Google + Booking) — same object shape, native ratingScale echoed (Google 5, Booking 10). Every tool below is read-only, annotated for Connectors, and validated by the same parsers the REST API uses.
search_staysDiscover hotels by location, dates, occupancy & filters across every OTA; prices embedded when dates are given.
check_availabilityDay-by-day availability for known listing(s) on one platform over a date range.
get_listingFull detail — amenities, photos, star rating, guest rating — for one hotel, with optional live price.
get_priceA price quote for one hotel for specific dates and occupancy.
compare_pricesCross-OTA rate comparison for one hotel (Google backbone); returns offers + computed min/median.
get_reviewsNormalized, paginated reviews for one hotel on one platform.
get_jobPoll status and results of an async scrape job — always costs 0 credits.
A hotel agent gets the identical object for a Google-Hotels property and a Booking.com one — read ratingScale so a 4.6/5 is never mis-compared to a 9.4/10. Pair search_stays with compare_prices to rate-shop a single hotel across every OTA. All tools are read-only, OAuth-scoped, and metered on one balance; a failed or empty call costs 0 credits.
Self-serve access
Add one URL. Sign in with OAuth. No partner application.
The official hotel APIs (EPS Rapid, Booking.com Connectivity) are partner-gated — application, approval, contract. ScoutingAPI is self-serve: add mcp.scoutingapi.com as a remote server or Connector, sign in once with OAuth 2.1 / PKCE, and every tool call is authenticated and metered on your account.
100 free credits — no credit card
Enough to wire the server into your hotel agent and test every tool against real responses before you decide anything.
scout_test_ sandbox at zero cost
Point the server at your sandbox key for deterministic fixtures while you build the agent — zero spend.
One balance for every tool & OTA
OAuth resolves your account and meters each call on one credit ledger — no separate billing per platform or per tool.
- 1Get your free key
- 2Add mcp.scoutingapi.com + OAuth
- 3Let the agent call the tools
The trust wedge
A hotel MCP server you can put in production.
A hotel agent is only as reliable as its tools. Scraper-backed MCP servers have no SLA and pay-per-attempt billing; gated APIs make you wait for approval. We run a product — monitoring, failover, retries, caching, and OAuth — behind one contract.
99.9% monthly uptime SLA
Committed on the ScoutingAPI response envelope and published on a public status page. Multi-actor failover, retries, and caching sit behind one server.
Failed tool calls cost 0 credits
A blocked or unreachable OTA returns a typed upstream_unavailable (or meta.partial) and we charge nothing — so a flaky OTA never runs up your agent’s bill.
OAuth 2.1 / PKCE, read-only
Every tool is read-only and scoped by an OAuth access token — Connectors-ready, with the token → account → billing bridge handled server-side.
Connect in five minutes
Add it to Claude, Cursor, or n8n.
Add the server URL to your MCP client and sign in with OAuth — the seven tools appear automatically. Same server, same tools, any client.
{
"mcpServers": {
"scoutingapi": {
"url": "https://mcp.scoutingapi.com",
"transport": "http"
}
}
}mcp.scoutingapi.com speaks Streamable HTTP with OAuth 2.1 / PKCE, so it works as a remote server in Claude Desktop and Cursor and as a custom Connector in Claude. The tools are advertised with human titles and read-only hints (a Connectors requirement), so the agent picks the right one.
The honest comparison
Hotel MCP: open-source repo, bolt-on, gated hotel API, or ScoutingAPI?
| Capability | ScoutingAPI MCP | Open-source MCP | Scraper + bolt-on MCP (Apify) | Gated hotel API (EPS Rapid) |
|---|---|---|---|---|
| Access | Self-serve + OAuth in minutes | Clone & self-host | Self-serve, per-actor | Partner-gated (application + contract) |
| OTA coverage | Booking, Google & more — one server | Usually one source | One platform per actor | Own inventory only |
| Cross-OTA rate-shopping | Yes — compare_prices, min/median | No | No | No (own inventory) |
| Tools | 7 read-only, Connectors-annotated | A few, unannotated | Per-actor, varies | n/a (REST, not MCP) |
| Auth | OAuth 2.1 / PKCE | None (runs locally) | API token per actor | Partner credentials |
| Reliability | 99.9% SLA, status page, failover | None — community-maintained | None (~86% success, no SLA) | Platform-dependent |
| Failed-call billing | Free — 0 credits | n/a | You pay per attempt | n/a |
| Setup | Add one URL + OAuth sign-in | Clone repo, run locally, self-host | Bolt MCP onto each actor | Apply, wait, integrate |
The honest read: open-source hotel MCP servers barely exist and are unauthenticated; a scraper’s bolt-on MCP inherits its per-actor, pay-per-attempt shape; the official hotel APIs make you apply and only expose their own inventory. ScoutingAPI is the self-serve hotel MCP with cross-OTA rate-shopping, OAuth, one balance, and an SLA.
Built for real agents
What builders ship on the hotel MCP.
Not “an MCP demo” — the hotel-agent workflows a specific builder recognizes.
Cheapest-rate hotel concierge
The agent uses search_stays to shortlist hotels and compare_prices to return the cheapest cross-OTA rate per property — the answer, not a list of links.
Hotelier rate-parity monitoring
Wire compare_prices into a workflow that watches a hotel’s rate across every OTA for the same dates and flags parity gaps — OAuth-secured.
Corporate travel-desk agents
Give a travel-desk copilot hotel search, price quotes, and reviews in one authenticated session so it books within policy and budget.
Hotel price-watch automations
Poll compare_prices for a booked hotel and ping the traveler when a cheaper rate appears — shippable from n8n in minutes.
Hotel market-rate intelligence
Track how hotel rates move across OTAs for a destination and date range to brief a pricing or revenue decision.
Review-aware recommendations
The agent pairs get_reviews with search_stays so it recommends hotels on both price and normalized guest sentiment.
Answers
Hotel MCP server — frequently asked questions
The questions agent builders actually search — answered in full, with FAQ structured data for rich results.
Give your hotel agent cross-OTA rate-shopping.
100 credits, no credit card. Add mcp.scoutingapi.com to Claude, Cursor, or n8n in under five minutes.
Seven read-only tools · cross-OTA rate-shopping · failed tool calls cost 0 credits