Little Hotelier MCP Server

Bookings, rates and availability for your Little Hotelier property.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/little-hotelier'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Little Hotelier API and MCP server: Let your AI agent run your Little Hotelier front desk.

Little Hotelier gives properties no API, no webhooks and no MCP server (checked 24 Oct 2026). Cotlet runs 15 Little Hotelier tools hosted, over MCP for agents and REST for scripts.

Read Little Hotelier reservations, room inventory and reports from your own hotel account. Connect agents through MCP or reporting workflows through REST.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Little Hotelier or SiteMinder
Page: https://cotlet.dev/integrations/little-hotelier-api-mcp-server

What can you automate in Little Hotelier?

Check arrivals and unpaid balances
Bulk update rates for a date range
Set minimum stay and closed to arrival
Close a room for maintenance
Report occupancy, ADR and RevPAR
Reply to guest messages

Does Little Hotelier have an MCP server or an API?

SiteMinder's five APIs (pmsXchange, SiteConnect, Channels Plus, SMX, Direct Booking) need a partner agreement, and its developer page does not name Little Hotelier.
SiteMinder's Channels Plus MCP (April 2026) lets AI travel sites book your rooms. It does not read your reservations, change rates or answer guests.
Zapier and n8n have no Little Hotelier app. App Store apps each do one job, such as pricing or check-in.

What you need	App Store app	Your own script	Cotlet
Read reservations and balances	Inside that app	If you write it	Yes, as data
Change rates and restrictions	Rates, from a pricing app	If you write it	Yes, after your OK
Answer Messaging hub threads	Booking engine chat only	If you write it	Yes, after your OK
Statistics and channel reports	Some apps	If you write it	Yes
Session and MFA handled for you	Yes, official link	Cookie expires, MFA every 30 days	Cloud Browser keeps it

Checked 24 Oct 2026. Sources: SiteMinder APIs and who they are for, SiteMinder AI distribution (Channels Plus MCP), Supergood API report card: Little Hotelier, Little Hotelier App Store

How does Cotlet connect to Little Hotelier?

Sign in to Little Hotelier. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your Little Hotelier password, and no rate, restriction or guest reply goes out until you approve it.

Connect Little Hotelier to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Turn on Little Hotelier for agents. Create a Cotlet account, sign in to Little Hotelier in its Cloud Browser and press Enable for agents.
Give your agent the address. Put https://cotlet.dev/mcp/v1 in the MCP server or connector field of your agent.
Log in to Cotlet or use a key. Chat apps open a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console.

Little Hotelier sits on the shared address https://cotlet.dev/mcp/v1 with any other app you enable. Enabled it after you connected? Refresh the connector and the 15 tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-little-hotelier \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-little-hotelier": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-little-hotelier]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: little_hotelier_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: little_hotelier_write

How to use the Little Hotelier REST API

Create your Cotlet API key

Create a Cotlet API key with access to Little Hotelier and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Sign in to Little Hotelier in its Cotlet Cloud Browser and enable the app for agents. Your login needs access to Front Desk, Channel Manager or Insights for the operations you choose.

Make your first Little Hotelier API request

REST:

curl "https://cotlet.dev/api/v1/little-hotelier/reservations?limit=2" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read reservations and continue the list

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "little-hotelier",
  "tool": "list_reservations",
  "result": {
    "reservations": [
      {
        "reservation_id": "LH48213",
        "status": "confirmed",
        "guest": "Marta Kowal",
        "source": "Booking.com",
        "occupants": "2 adults",
        "check_in": "2026-10-12",
        "check_out": "2026-10-14",
        "booked": "2026-09-02",
        "room": "Double 3",
        "total": "240.00",
        "outstanding": "240.00",
        "currency": "EUR"
      }
    ],
    "next_cursor": null
  }
}

Read result.reservations and pass result.next_cursor unchanged as cursor until null. Keep date type, date range, status and guest filters fixed.

Reservation pages default to 50 records, with a maximum of 200. Preserve currency and compare status, stay dates and outstanding amounts when updating a report.

A reservation can be cancelled or have no assigned room. Report exports accept date ranges of at most 365 days.

Little Hotelier workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Combine reservations and reservation details into an arrivals briefing with stay dates and outstanding balances.
Make	HTTP > Make a request	Read room rates and inventory for selected dates into an availability report without changing rates.
Python or Node.js	REST API	Combine statistics and booking performance into an occupancy and cancellation report for your chosen sheet.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Little Hotelier; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Little Hotelier API endpoints and MCP tools

Front Desk reservations

Card numbers never come back. Booking.com, Expedia and Airbnb bookings are cancelled on the channel, so cancel_reservation refuses them.

List reservations (list_reservations, read): Reservations with status, source, guest, occupants, dates, room, total and outstanding amount.
Get reservation (get_reservation, read): One reservation: stay, room, rate, guests, guest comments, notes, invoice and payments. No card numbers.
Create reservation (create_reservation, write, asks first): New Front Desk reservation. No card details.
Update reservation status (update_reservation_status, write): Check a guest in or out, or set a reservation back to Confirmed.
Cancel reservation (cancel_reservation, write, asks first): Cancel a Confirmed Front Desk reservation. Permanent; OTA bookings must be cancelled on the channel.

Rates, restrictions and room closures

Changes reach your connected channels inside each channel's update period. Derived rates are skipped and follow their base rate.

List room rates (list_room_rates, read): Room types, their rooms and room rates, with which rates are derived.
Get inventory (get_inventory, read): The inventory grid for a date range: availability, rates and restrictions per room rate.
Update rates (update_rates, write, asks first): Set the base rate of room rates over a date range, like Bulk Update. Goes live on your channels.
Update restrictions (update_restrictions, write, asks first): Set min or max stay, closed to arrival or departure, or close channels or your website.
Create room closure (create_room_closure, write, asks first): Close rooms for a date range; availability sent to channels and the booking engine drops.

Statistics and reports

Occupancy and RevPAR exist only when searching by stay date. One export covers at most 365 days.

Get statistics (get_statistics, read): Statistics report: room nights, occupancy, ADR, RevPAR, length of stay, lead time and cancellations.
Get booking performance (get_booking_performance, read): Revenue, reservations, room nights, ADR and cancellations, broken down by channel.
Export report (export_report, read): A Front Desk report for up to 365 days as rows, the same data as its CSV export.

Messaging hub

Needs the Guest Engagement add-on. Email and SMS replies land in your inbox, not here.

List conversations (list_conversations, read): Messaging hub conversations with the linked reservation, channel and last message.
Reply to guest (reply_to_guest, write, asks first): Send a reply in a Messaging hub conversation. WhatsApp free-form only within 24 hours of the guest message.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/little-hotelier-api-mcp-server#tools

Who can see my Little Hotelier session, and how do I revoke it?

What we store. The signed-in Little Hotelier profile, encrypted with AES-256-GCM, in Finland. Never the password.
What your agent gets. The 15 Little Hotelier tools, not the cookie and not guest card numbers.
What the session sees. What that Little Hotelier user may open: bookings, guest emails, rates, reports.
What no tool touches. Card details, payouts, billing, users, MFA and channel mapping.
When MFA comes up. Little Hotelier asks every 30 days. You approve it in your app; we never do.
How to cut access. Disable for agents, reset the browser, or disable that user under Manage users.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet.

Is it against Little Hotelier's terms? Account safety

Each staff member must have their own user account with a unique email address. The system automatically blocks logins when it detects unusual activity.

Little Hotelier Help Centre, Troubleshooting login issues, read 24 Oct 2026

SiteMinder's customer terms, which cover Little Hotelier, say nothing about bots or scraping. Clause 3.3 lets "Customer Users" use the product, and the definition includes your "agents, contractors or representatives". Clause 3.7 makes each login "personal". So the safe setup is a Little Hotelier user of its own for the agent, created by you with only the permissions its tools need. We found no public case of a Little Hotelier account closed for automation (checked 24 Oct 2026).

How we keep your property account calm:

A user you create and sign in yourself, not a shared staff login
One Cloud Browser with steady cookies and IP, so no surprise MFA prompts
Rates, restrictions, closures and guest replies wait for your OK
No tool reads card numbers, edits users or changes channel mapping
If SiteMinder objects, we pause the Little Hotelier tools for everyone within 24 h

A rate sent to Little Hotelier goes on to Booking.com, Expedia and your booking engine. Change a season in a few grouped calls, not hundreds of single nights.

What happens when Little Hotelier changes?

12 h between tests of the reservation and report reads
24 h between tests of writes that reach channels or guests
$0 for a call to a Little Hotelier tool paused for repair

Little Hotelier signs you in on a SiteMinder page and asks for MFA every 30 days, and its screens keep changing. When one moves, we repair the tool and your scheduled runs keep their prompts. status.cotlet.dev watches the site, console and API every 3 minutes.

Approvals, undo and mistakes

Saves the old prices. get_inventory keeps every night as it was.
Groups the nights. One update per price, rate set and weekdays.
Waits for your OK. Each grouped change sits in your Cotlet console.
Checks the grid. Reads the nights again and lists any that did not save.

Action	Undo
Update rates	Send the saved old price; bookings made meanwhile keep the new one
Update restrictions	Run it again with the old values
Close a room	Remove the closure on the Front Desk Calendar
Create a reservation	Cancel it; the room goes back on sale
Check in or out	Set the status back, no guest is told
Cancel a reservation	No, permanent
Reply to a guest	No, the message is out

6 of 15 tools ask first: everything that reaches a channel, a booking or a guest. update_reservation_status runs at once, since the desk changes it all day and one call sets it back. You can switch the wait off per tool for a scheduled run.

Little Hotelier keeps no history of rate values, so the before snapshot from get_inventory is your only record of the old price.

MCP call:

{
  "name": "update_rates",
  "arguments": {
    "room_rate_ids": [
      "rr_20417"
    ],
    "from": "2026-12-01",
    "to": "2026-12-31",
    "rate": "140.00",
    "days_of_week": [
      "fri",
      "sat"
    ]
  }
}

REST:

curl -X PATCH https://cotlet.dev/api/v1/little-hotelier/rates \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"room_rate_ids":["rr_20417"],"from":"2026-12-01","to":"2026-12-31","rate":"140.00","days_of_week":["fri","sat"]}'

Tool output:

{
  "status": "updated",
  "room_rates": 1,
  "dates": 8,
  "rate": "140.00",
  "currency": "EUR",
  "skipped": []
}

A nightly pricing script or a cron job calls the same tools over REST at /api/v1/little-hotelier, with one key and one price. A rate under your property minimum does not save, and a failed call costs nothing. The tools table lists the REST path of each tool.

How much does the Little Hotelier MCP server cost?

About $25 a month for a 10-room B&B, 4,260 credits. SiteMinder bills your Little Hotelier plan as before.

Job	Calls	Credits
Arrivals and unpaid balances, daily	3 × 30	900
Answer waiting guest messages, daily	5 × 30	1,500
Set next week's rates, weekly	5 × 4	200
Min stay and CTA for an event	4 × 2	80
Occupancy, ADR and channel report, weekly	2 × 4	80
Cloud Browser, 30 days		1,500
Total		4,260

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
Any Little Hotelier plan; guest replies need Guest Engagement

The property is our example: 10 rooms, about 65% occupancy, 2.5-night stays, so 2 to 3 arrivals a day. Little Hotelier is built for 1 to 30 rooms and publishes no average. A season of rates is a few grouped calls, not one per night. Dollars at the $29 pack rate.

Little Hotelier MCP server on GitHub, Zapier or hosted: which to use

Option	What it does	Where it stops
lh-rate-automation	One property's Apps Script: formula prices pushed nightly with a copied session cookie.	Rates only, no license, 0 stars. The cookie has to be kept alive by hand.
Hotelier Tools	Browser userscripts and a dashboard for check-out, payment checks and invoices.	You send it a username and password. Free until 9 Jan 2027, then 50 € a month.
Supergood	Builds an unofficial API on the web app, per customer.	Made to order, no public price.
RoomPriceGenie and other App Store pricing apps	Revenue management that pushes rates through SiteMinder.	Rates only, about €198 to €440 a month.
Zapier, n8n	Nothing: no Little Hotelier app.	Both pages answer 404.

Nobody else runs a Little Hotelier MCP server, on GitHub or hosted. A pricing app covers rates well and nothing else. A cookie script is one property's hobby until the session or MFA expires. Cotlet gives your agent reservations, rates, reports and the Messaging hub in one place, in the account you already pay for.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273), working since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Little Hotelier tools go to contact@cotlet.dev.

Little Hotelier API and MCP: questions

Can I use the Little Hotelier API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Sign up free at https://cotlet.dev, open Little Hotelier under Integrations in the console and sign in to Little Hotelier in its Cloud Browser. The trial starts when you sign up and asks for no card.

How do I connect Little Hotelier to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Little Hotelier once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Little Hotelier account through Cotlet, in their phone apps too.

What can ChatGPT do in Little Hotelier?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Little Hotelier: check today; update hotel rates for a date range; set minimum stay and closed-to-arrival. You ask in plain words, and anything that reaches other people waits for your OK first.

Can my agent cancel Booking.com or Airbnb reservations?

No. Little Hotelier only lets staff cancel reservations created in Front Desk; channel reservations are cancelled by the guest on the channel. cancel_reservation fails for them.

Should the agent use my own Little Hotelier login?

Better a user of its own. Little Hotelier wants one user per person or agent, and blocks logins it finds unusual. Create the user under Manage users with only the permissions the tools need, set up its MFA, and sign it in once in the Cloud Browser.

Does it work with Little Hotelier MFA?

Yes. MFA is mandatory in Little Hotelier and comes back every 30 days or on a new browser. The Cloud Browser keeps its cookies, so you approve it about once a month in the Little Hotelier app or your authenticator. We never enter codes for you.

Can the agent see guest card numbers?

No. get_reservation returns the invoice, payments and balance, never card details, and no tool accepts them.

Is the MCP server different from the REST API?

Only the door differs. Both carry the same 15 tools, inputs and answers with one key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Little Hotelier?

No. Cotlet is independent and not affiliated with Little Hotelier or SiteMinder Limited.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.