Hostelworld MCP Server

为旅舍业主提供评价、住客消息和预订管理。

托管 MCP 服务器

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

可安装到 Claude Code、Codex、Cursor 等客户端

文档

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

Hostelworld API and MCP server: Let your AI agent clear your Hostelworld Inbox.

Hostelworld has no MCP server and no API a property can call for reviews, Property Chat, no-shows or PayNow (checked 27 Oct 2026). Cotlet runs 15 Hostelworld tools hosted, over MCP for agents and REST for scripts.

Read Hostelworld property bookings and guest conversations through MCP or REST. Connect your Inbox account to an agent or a private operations report.

MCP setup REST API guide

What can you automate in Hostelworld?

  • Reply to guest reviews
  • Answer Property Chat questions
  • Mark no-shows before 23:59
  • Acknowledge new bookings
  • Match PayNow payouts to bookings
  • Report unpaid balances

Does Hostelworld have an MCP server or an API?

  • Properties connect only through a channel manager Hostelworld has approved. Hostelworld switches the link on and emails a separate API password; it carries rates, availability and bookings.
  • The affiliate API (property search, details, reviews, links) is for sites that sell beds, and is given "on a case by case basis".
  • Zapier and n8n have no Hostelworld app. Every "Hostelworld MCP" we found scrapes public listings, not your Inbox.
What you needChannel managerApify or Bright DataCotlet
Rates and availabilityYes, its main jobNoNo, keep your channel manager
Read and acknowledge bookingsYesNoYes, after your OK
Reply to or query reviewsNoReads public reviewsYes, after your OK
Property Chat with guestsNoNoYes, after your OK
No-shows, payment issues, PayNowNoNoYes

Checked 27 Oct 2026. Sources: Hostelworld Affiliate Programme: Solutions (API on request), Hostelworld Help: Connecting through a channel manager, Hostelworld Help: Reply to or query a review, Hostelworld Help: Property Chat FAQ, Hostelworld Help: Marking customers as no-shows, Hostelworld Help: PayNow guide, Hostelworld Help: How to charge if a customer does not arrive, Hostelworld Help: How long does a review stay on my page, BookingAutomation: Hostelworld connection and API password, Bright Data Hostelworld MCP (public data)

How does Cotlet connect to Hostelworld?

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

We never keep your Inbox password, and no review reply, chat message or no-show goes out until you approve it.

Connect Hostelworld 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.

  1. Open Hostelworld in Cotlet. Make a Cotlet account, sign in to your Hostelworld Inbox in its Cloud Browser, then press Enable for agents.
  2. Add the Cotlet address. Your agent's MCP or connector settings take https://cotlet.dev/mcp/v1.
  3. Sign in to Cotlet or add a key. Chat apps ask you to log in to Cotlet. Editors, n8n and scripts use an API key from the console.

Hostelworld shares the address https://cotlet.dev/mcp/v1 with every other app you enable. Turned it on after connecting? Refresh the connector to see the 15 tools.

Claude:

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

Claude Code:
claude mcp add --transport http cotlet-hostelworld \
  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-hostelworld": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-hostelworld]
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: hostelworld_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: hostelworld_write

How to use the Hostelworld REST API

Create your Cotlet API key

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

Sign in to Hostelworld in its Cotlet Cloud Browser and enable the app for agents. Use your property Inbox login; PayNow and payout operations require a Manager user.

Make your first Hostelworld API request

cURL:

curl "https://cotlet.dev/api/v1/hostelworld/new-bookings?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read the new-booking queue and older records

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": "hostelworld",
  "tool": "list_new_bookings",
  "result": {
    "bookings": [
      {
        "booking_ref": "412-305871264",
        "guest": "Jan Kowalski",
        "arrival": "2026-10-18",
        "nights": 2,
        "booked_at": "2026-10-10T21:14:00Z"
      }
    ],
    "next_cursor": null
  }
}

Read result.bookings and pass result.next_cursor unchanged as cursor until null. New-booking pages default to 50 records, with a maximum of 100.

Acknowledged bookings leave the new queue, including those acknowledged by a channel manager. An empty queue does not mean the property has no reservations.

Use search_bookings with arrival or booked-date filters for acknowledged records. Compare booking state and arrival dates as well as references; booking details do not return card information.

Hostelworld workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestRead new bookings and booking details into an arrivals brief without acknowledging bookings.
MakeHTTP > Make a requestSearch bookings and read their details into a dated arrival report that also includes acknowledged reservations.
Python or Node.jsREST APIRead property chats and chat details into a private guest-reply queue without sending messages.

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

Cotlet reads Hostelworld; 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.

Hostelworld API endpoints and MCP tools

Bookings, no-shows and payment issues

No card data comes back. With a channel manager, New Bookings is usually empty because bookings are acknowledged there.

  • List new bookings (list_new_bookings, read): Bookings in the New Bookings tab that you have not acknowledged yet.
  • Search bookings (search_bookings, read): Advanced Search by arrival or booked date, or by reference, guest name or email.
  • Get booking (get_booking, read): Booking details: guest, dates, rooms or beds, rate type, deposit paid, balance due and status. No card data.
  • Acknowledge booking (acknowledge_booking, write, asks first): Click "I have read this booking" so the booking leaves the New Bookings tab and Hostelworld knows you picked it up.
  • Mark as no-show (mark_no_show, write, asks first): Cancel a booking as a no-show and email the guest. Available from the check-in date, not for Pay Now.
  • Report payment issue (report_payment_issue, write, asks first): Report Payment Issue on a booking: the guest gets an email asking them to pay.

Reviews from Customer Ratings

One request covers up to a year. Hostelworld checks each reply before it shows, and a sent reply cannot be edited.

  • List reviews (list_reviews, read): Reviews from Reports > Customer Ratings, with ratings, text, booking reference and whether you replied.
  • Reply to review (reply_to_review, write, asks first): Public reply under a review. Hostelworld checks it before publishing and it cannot be edited after.
  • Query review (query_review, write, asks first): Send a review to a Hostelworld moderator when you believe it breaks the review guidelines.

Property Chat

Opt in under Chats first. Only guests on the iOS app can chat; text only, read-only after check-out.

  • List guest chats (list_chats, read): Guest chats in the Inbox, newest first, with booking reference and unread flag.
  • Get chat (get_chat, read): All messages in one guest chat, and whether it is still open or read-only after checkout.
  • Send chat message (send_chat_message, write, asks first): Reply to a guest in Property Chat, or start a chat from a booking when the Chat option is available.

PayNow payouts

Needs a Manager user. Reads only: no tool changes PayNow settings or bank details.

  • List payouts (list_payouts, read): PayNow payouts from Property Setup > Finance > Pay Now: date, status, amount, masked bank account, plus balance and next payout date. Manager users only.
  • Get payout (get_payout, read): One payout: timeline, Payout Trace ID, charges, refunds, adjustments, fees, net amount and every payment it includes.
  • Export guest payments (export_guest_payments, read): Guest Payments export as a CSV download link, with booking IDs for reconciliation. Manager users only.

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

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

  • What we store. Your signed-in Inbox profile, AES-256-GCM, in Finland. Not the hostel number or password.
  • What your agent gets. The 15 Hostelworld tools. Never the cookie, never CC details.
  • What the session sees. What that Inbox user may open: bookings, reviews, chats, PayNow for a Manager.
  • What no tool touches. Guest cards, rates, Service Fee and Elevate, users, PayNow settings.
  • When Inbox wants a new login. Hostelworld emails a secure link. You open it; we never read your mail.
  • How to cut access. Disable for agents, reset the browser or delete the key. The next call stops.

cotlet.dev has A+ grades on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.

Is it against Hostelworld's terms? Account safety

The Licensee is responsible to HW for all activities carried out under the Login, whether such activities are carried out by authorised individuals or not.

Hostelworld Services and Licence Programme Agreement, clause 1.9, read 27 Oct 2026

The agreement your hostel accepted names no bots or scraping. Clause 1.8 lets only people you authorise use the Login, and 10.4.5 lets Hostelworld suspend Inbox for a breach of clause 1. The site's General Terms (updated 30 Sep 2021) go further: 7.4(a) bans reaching site content "using any robot, spider, scraper or other automated means" without written permission. We found no public case of a property suspended for automation (checked 27 Oct 2026).

How we keep your Inbox calm:

  • Your own Login, signed in by you with the secure link
  • One Cloud Browser with steady cookies and IP
  • Review replies, chats, no-shows and payment requests wait for your OK
  • No tool touches rates, the Service Fee, Elevate or guest cards
  • If Hostelworld objects, we pause the Hostelworld tools for everyone within 24 h

Clause 10.4.4 ends the agreement for fake reviews. The agent answers reviews; it never writes, edits or asks for one.

What happens when Hostelworld changes?

  • 12 h between tests of the booking, review and payout reads
  • 24 h between tests of writes a guest or Hostelworld sees
  • $0 for a call to a Hostelworld tool paused for repair

Inbox grows new tabs: Chats came with Property Chat, PayNow sits under Property Setup > Finance. When a screen moves, we fix the tool and your prompts stay as they are. status.cotlet.dev watches the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Lists the arrivals. Today's bookings next to your check-in list.
  2. Skips the wrong ones. Pay Now, cancelled, part groups, late-arrival chats.
  3. Waits for your OK. Each no-show sits in your Cotlet console.
  4. Says whom to charge. Names, rate type and how long the card stays.
ActionUndo
Acknowledge a bookingNo; it stays in Inbox and in search
Reply to a reviewNo, locked once sent
Query a reviewNo; the moderator decides
Send a chat messageNo, the guest has it
Report a payment issueNo, the guest is emailed
Mark as no-showNot with a tool; the booking is cancelled

All 6 write tools of 15 ask first, because every one reaches a guest or Hostelworld and none can be reversed by a tool. The 9 reads run at once. Once a scheduled job has gone right a few times, you can switch the wait off for that tool.

On a one-night booking the Mark as No-Show button is gone after 23:59 on arrival day, so a late-evening run leaves time for your OK.

MCP call:

{
  "name": "reply_to_review",
  "arguments": {
    "booking_ref": "412-305871264",
    "body": "Thanks for staying with us! We have fixed the hot water in dorm 3 since your visit. Hope to see you again."
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/hostelworld/bookings/412-305871264/review/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Thanks for staying with us! We have fixed the hot water in dorm 3 since your visit. Hope to see you again."}'

Tool output:

{
  "booking_ref": "412-305871264",
  "status": "pending_moderation",
  "submitted_at": "2026-10-11T14:22:05+02:00",
  "editable": false
}

A cron job or your PMS can call the same tools over REST at /api/v1/hostelworld, with one key and one price. A PayNow call from a non-Manager user fails and costs nothing. The tools table lists the REST path of each tool.

How much does the Hostelworld MCP server cost?

About $26 a month for a 40-bed hostel, 4,520 credits. Hostelworld's Service Fee on bookings stays as it is.

JobCallsCredits
Acknowledge new bookings, daily3 × 30900
Answer Property Chat, daily3 × 30900
No-show check at 22:30, daily3 × 30900
Reply to new reviews, weekly5 × 4200
Match the PayNow payout, weekly3 × 4120
Cloud Browser, 30 days1,500
Total4,520
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works next to your channel manager, no change to it

The hostel is our example. Hostelworld had 7.0M net bookings in 2025 across about 17,000 properties, so about 35 a property a month, and 66% of its hostels have 50 beds or fewer. The 15 reviews a month are our guess. Dollars at the $29 pack rate.

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

OptionWhat it doesWhere it stops
Channel managers (myallocator, NOBEDS, Channex and others)Rates, availability and bookings, on an API password Hostelworld issues to them.Their Hostelworld guides cover no reviews, Property Chat, no-shows or PayNow.
Apify Hostelworld actorsPublic listings, prices and reviews, also as MCP; from $1.50 per 1,000 rows.Traveller-side data only. They cannot sign in to Inbox or reply.
Bright Data Hostelworld MCPPublic prices, availability and reviews; $1.50 per 1,000 requests, 5,000 free a month.Same: public pages, no property account.
sirstudly/littlehotelierOne hostel group's Java jobs, including an Inbox scraper.Not an MCP server, no README or license, 1 star.
Zapier, n8nNothing: no Hostelworld app.Both pages answer 404.

No one else runs an MCP server on the property side of Hostelworld. Keep your channel manager for rates and availability. Use a scraper to watch competitors' prices. Use Cotlet when your agent should answer reviews and chats, mark no-shows and check PayNow in your own Inbox.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Hostelworld tools.

Hostelworld API and MCP: questions

Can I use the Hostelworld 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 Hostelworld under Integrations in the console and sign in to your Inbox in its Cloud Browser with your hostel number, username and password. The trial starts when you sign up, no card asked.

How do I connect Hostelworld to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Hostelworld 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 Hostelworld account through Cotlet, in their phone apps too.

What can ChatGPT do in Hostelworld?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Hostelworld: log new bookings to a spreadsheet; reply to guest reviews; answer guest chats. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need a channel manager or an API key from Hostelworld?

No. Cotlet works in your own Hostelworld Inbox account. Hostelworld offers its API case by case to affiliates and connects properties through channel managers only (checked 11 Oct 2026). With a channel manager, bookings are acknowledged there, so New Bookings is empty.

Who can use the PayNow tools?

Only Manager user accounts in Inbox can view PayNow payouts and the Guest Payments export, so list_payouts, get_payout and export_guest_payments need a Manager login.

Does it replace my channel manager?

No. It has no tools for rates or availability. Your channel manager keeps those; Cotlet works on what the channel connection leaves in Inbox: reviews, Property Chat, no-shows, payment issues and PayNow.

Can the agent see guest card numbers?

No. get_booking returns the deposit paid and the balance due, never card details, and no tool charges a card. You charge a no-show fee yourself from CC details in Inbox.

Can it change my Service Fee or Elevate level?

No. No tool opens Elevate, the Service Fee or your ranking settings. Those stay with you in Inbox.

Is the MCP server different from the REST API?

The door differs, nothing else. 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 Hostelworld?

No. Cotlet is independent and not affiliated with Hostelworld.com Limited or Hostelworld Group.


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.