HolidayCheck MCP Server
HolidayCheck Model Context Protocol

Get HolidayCheck hotel data by chatting with AI.

Paste one prompt into Claude Code, Cursor, or your agent and it installs itself. Your agent then pulls HolidayCheck data from plain-English prompts. Same API key, same billing as the REST API.

50 free requests on signup No credit card Any language, no code

Trusted by hospitality teams at

What you can ask

Ask in plain English.
Get real HolidayCheck answers.

Whatever you'd ask a junior analyst about a hotel, ask your agent. No syntax to learn.

>

Find Alexa Hotel by name and show its descriptions, amenities, and check-in information.

>

Extract the hotel UUID from this HolidayCheck hotel URL.

>

Read the newest reviews for Alexa Hotel and summarize recurring topics.

>

Compare the native six-point rating with the recommendation percentage.

Behind the scenes

You type plain English. Your agent calls the right HolidayCheck tool.

Real examples. You ask, the agent picks a tool and fills the parameters, you read the answer. These outputs are illustrative.

01 Search and details
You ask

Find Alexa Hotel on HolidayCheck and show its amenities and check-in information.

Behind the scenes holidaycheck_hotels_search(query="Alexa Hotel", page=1) -> holidaycheck_hotel_details(hotel_id=...)
You see

Hotel-name matches with UUIDs, followed by descriptions, grouped amenities, location, contact, star classification, and native guest-rating summary.

02 URL to ID
You ask

Extract the hotel UUID from this HolidayCheck URL.

Behind the scenes holidaycheck_hotel_url_to_id(url=...)
You see

A lowercase hotel UUID and normalized supplied URL, without an existence check.

03 Reviews
You ask

Summarize the newest HolidayCheck reviews for Alexa Hotel.

Behind the scenes holidaycheck_hotel_reviews(hotel_id="c6b63919-17b1-317d-a9e7-e69dbe195f2e", page=1, sort="recent_desc")
You see

Up to 10 reviews with native six-point ratings, text sections, review timestamps, and stay months.

Connect it

Paste one sentence. Your agent does the rest.

Copy the prompt into the agent you already have open. It reads our setup page and wires up the connector itself.

Paste into Claude Code
Read https://stayapi.com/install and set up the StayAPI MCP server for me.

Then open a new session and run claude mcp list — stayapi should read ✓ Connected.

No key yet? Sign up for 50 free requests — the agent asks you for it.

Claude on the web, desktop, or mobile doesn't need this prompt: add StayAPI under Settings → Connectors and sign in. Other clients: manual setup below.

No key

Claude on the web, desktop & mobile

Add StayAPI as a connector and sign in. Nothing to paste.

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Name it StayAPI and set the URL to https://api.stayapi.com/mcp.
  3. Click Connect, sign in to StayAPI, and choose Allow.
Manual setup — paste the config yourself
01

Claude Code

One terminal command.

bash
claude mcp add --scope user --transport http stayapi https://api.stayapi.com/mcp --header "X-API-Key: YOUR_API_KEY"
  1. Run the command in any terminal.
  2. Open a new Claude Code session.
  3. Confirm with claude mcp list.
02

Cursor

Edit ~/.cursor/mcp.json.

json
{
  "mcpServers": {
    "stayapi": {
      "type": "http",
      "url": "https://api.stayapi.com/mcp",
      "headers": { "X-API-Key": "YOUR_API_KEY" }
    }
  }
}
  1. Open or create the file.
  2. Paste, swap YOUR_API_KEY, save.
  3. Restart Cursor.
03

Claude Desktop

Edit claude_desktop_config.json.

json
{
  "mcpServers": {
    "stayapi": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote@0.1.18",
        "https://api.stayapi.com/mcp",
        "--header", "X-API-Key:YOUR_API_KEY"
      ]
    }
  }
}
  1. Open the config file in your OS.
  2. Paste, swap the key, save.
  3. Quit Claude with ⌘ Q, relaunch.

On Windows, a bare npx can fail with spawn npx ENOENT. Use the absolute path to npx.cmd. Windows setup notes →

Full reference — every tool, error shapes, Windows notes: MCP documentation →

Tools for HolidayCheck

The HolidayCheck tools your agent can call.

Most agents pick the right tool from your prompt, so you never name it. One tool call counts as one request, the same as a REST request.

holidaycheck_hotels_search

Find hotels by query (1–200 characters after trimming), with page default 1 and up to 10 matches per page. available_count and has_more describe the available result set, not a global total. Pass returned hotel_id directly to details or reviews. No dates, prices, or destination search.

holidaycheck_hotel_details

Read hotel details by hotel_id UUID: canonical URL, address, location, contact, descriptions, grouped amenities, and check-in/out wording. Star classification is separate from native six-point guest ratings. No prices or photo gallery. Each successful call costs one credit.

holidaycheck_hotel_url_to_id

Extract a hotel UUID from a supported HolidayCheck hotel or review-listing URL. Does not verify hotel existence.

holidaycheck_hotel_reviews

Read HolidayCheck reviews by hotel_id UUID, with page (default 1) and sort most_relevant (default) or recent_desc. Up to 10 reviews per page, native six-point ratings, text sections, and recommendation percentage. No language control or owner responses.

Full parameters and response shapes live in the MCP docs. For the same data over REST, see the HolidayCheck API hub.

Point your agent at HolidayCheck.

Sign up, paste one prompt, let your agent install itself. Both paths end with your agent answering HolidayCheck questions in plain English.

01 · the fast path

Get your key

50 free requests on signup. Paste one prompt into your agent, then start asking it for HolidayCheck data.

Start free Read the MCP docs
  • 50 free requests, no credit card
  • Same key as the REST API
  • Any language, no code
02 · talk to us

Talk through your use case

15 minutes. We screen-share and wire Claude or Cursor to your real properties. Free of charge.

Book a demo
  • Working setup on the call
  • Your properties, your prompts
  • Engineering, not sales