MCP getting started#

The remote Hotelovia MCP server exposes the same published directory as the REST API through two read-only tools:

Tool	Purpose
`search_places`	Search a bounded page by country, city, text, lodging type, verification, and WhatsApp reachability.
`get_place`	Fetch one current published record by its Hotelovia id.
`show_place`	Display a public lodging card through an MCP App resource.
`show_place_search`	Display bounded lodging search results through an MCP App resource.

Remote server#

https://mcp.hotelovia.com/mcp

Create a key in the developer console, then supply it as a Bearer token in the MCP connection:

{
  "mcpServers": {
    "hotelovia": {
      "type": "http",
      "url": "https://mcp.hotelovia.com/mcp",
      "headers": {
        "Authorization": "Bearer htl_live_replace_me"
      }
    }
  }
}

Use your client's secret or environment-variable interpolation feature instead of committing the literal key to a configuration repository.

Local stdio transport#

The package can also run over stdio from this monorepo:

HOTELOVIA_API_KEY='htl_live_replace_me' \
  pnpm --dir hotelovia/mcp exec node stdio.js

Tool behavior#

Tool results include concise Markdown for the model and bounded structured content for hosts. Both tools call the versioned Hotelovia REST API, so their authentication, field meanings, publication boundary, cursors, and rate-limit behavior match the Places API.

No booking

An agent can find a place and its published contact details. It cannot check availability, see a price, or reserve anything: Hotelovia holds none of that. Ratings returned by a tool are Google's.

Outreach requests

An agent may use whatsappEligible to identify records for review. The MCP server does not send messages, establish consent, or approve outreach. Apply the outreach data boundary before acting on a result.