# MCP for AI agents

Choose the connection that matches your agent's job.



|  | Hotel search connector | Developer MCP |
| --- | --- | --- |
| Endpoint | https://www.hoteluse.dev/mcp/search | https://www.hoteluse.dev/mcp |
| Authentication | None | HotelUse bearer API key |
| Tools | search_hotels, get_room_rates, get_hotel | search_hotels, get_room_rates, get_hotel |
| Use case | Traveler hotel comparisons and booking links | Hotel search, room pricing and hotel information for applications |
| Billing | No HotelUse account credits; affiliate-supported | Developer signup credits, then prepaid usage |



## Public hotel search



```json
{
  "mcpServers": {
    "hoteluse": {
      "type": "streamable-http",
      "url": "https://www.hoteluse.dev/mcp/search"
    }
  }
}
```



Send flat arguments: `destination`, `check_in`, `check_out`, optional `rooms`, `currency`, `locale` and `residency_country`. Omitted rooms mean two adults in one room. The result includes a HotelUse ID for follow-up room requests and safe provider booking URLs. Use the MCP Apps resource for interactive four-row provider comparisons, or consume structured results directly.

## Brek multi-room booking

The public search connector links directly to Brek booking. Brek supports two or three rooms of the same supplier room type. HotelUse compares only those eligible Brek combinations for destination searches and room options; it does not combine separate one-room prices. Requests for more rooms can still return other supported providers. The authenticated developer API preserves raw supplier room combinations and its existing room-count limits.

## Three independent requests



```json
{
  "name": "search_hotels",
  "arguments": {
    "destination": "Bellevue, Washington",
    "check_in": "2026-11-12",
    "check_out": "2026-11-14",
    "currency": "USD",
    "rooms": [
      {
        "adults": 2,
        "children_ages": []
      }
    ]
  }
}
```



Search returns `data.view: "hotel_search"`, hotel summaries and provider minimum stay totals. No room options are included. The exact returned `hotel_id` identifies the hotel in follow-up calls.



```json
{
  "name": "get_room_rates",
  "arguments": {
    "hotel_name": "Hilton Bellevue",
    "destination": "Bellevue, Washington",
    "check_in": "2026-11-12",
    "check_out": "2026-11-14",
    "currency": "USD",
    "rooms": [
      {
        "adults": 2,
        "children_ages": []
      }
    ]
  }
}
```



Room queries return `data.view: "room_options"`, grouped room types, provider prices and rate terms for this hotel and itinerary. The consumer MCP returns all grouped room options and provider minimum prices in one call, with `room_options_complete: true` and `next_cursor: null`. `raw_offer_page` describes the included raw-offer sample; it does not indicate missing room groups. Do not fetch additional raw pages to answer ‘all room options and prices.’ Expand room cards locally. Raw supplier rate-plan pagination remains available through the authenticated developer API and developer MCP. Prefer a returned `hotel_id` when available; do not send both an ID and a hotel name. An exact ID is authoritative; optional destination, country and region hints carried over from search are accepted and do not change the selected hotel. A name must resolve to one active catalog record. Otherwise the tool returns `status: "hotel_selection_required"` with candidate IDs and requests no live rates.



```json
{
  "name": "get_hotel",
  "arguments": {
    "hotel_name": "Hilton Bellevue",
    "destination": "Bellevue, Washington",
    "locale": "en-US"
  }
}
```



The public metadata tool returns `data.view: "hotel_details"` and `data.hotel`: curated address, photos, facilities, descriptions, star classification, sourced guest ratings, consecutive positive review count, and pet/parking policies. Guest ratings identify their provider; review counts are not added across providers. A `fee: null` with `fee_status: "not_provided"` means the catalog has no exact amount. Paid parking and pets allowed do not imply any particular fee or restrictions. It needs no stay dates and makes no live supplier price call. It returns model-readable facts without a price comparison widget. Use these hotel facts to answer traveler questions without starting a price search.

## Supported developer tools



```json
{
  "mcpServers": {
    "hoteluse": {
      "url": "https://www.hoteluse.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HOTELUSE_API_KEY"
      }
    }
  }
}
```



Create an account and API key through the [Quickstart](/docs/quickstart.html). Store the key in your client's secret settings; exact header and environment syntax varies by client. Never commit it or expose it in browser code.

Begin with `search_hotels` and a destination. Use a returned hotel_id with `get_hotel` for hotel information or `get_room_rates` for room groups, prices and terms.

Developer tools use the HTTP request structures, including nested `context`. Consumer tools use flat itinerary arguments. The two schemas are intentionally distinct; read tools/list before calling.

[Full MCP reference](/docs/mcp.html) · [API reference](/docs/api/search-hotels.html) · [Pricing and limits](/docs/pricing-and-limits.html) · [Developer support](mailto:leo@hoteluse.dev?subject=HotelUse%20MCP%20support).

---

Canonical: https://www.hoteluse.dev/docs/mcp/ai-agents.html
Source: https://www.hoteluse.dev/docs/mcp/ai-agents.md