CuddlyNest Search & Listings MCP Server
Read-only MCP server for searching CuddlyNest hotels and retrieving hotel room, price, availability, and cancellation details.
Search hotels by destination with optional dates, guest counts, child ages, currency, hotels-only mode, and broader city hotel list.
Get place candidates and top hotel matches with names, listing URLs, star/guest ratings, images, distance from center, and amenities.
Retrieve a specific hotel’s static details plus room options, pricing, availability, and cancellation policies.
Look up hotels by CuddlyNest URL or numeric
product_id.Does not book, pay, or write data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@CuddlyNest Search & Listings MCP Server Search for hotels in Barcelona and show prices for 2 adults this weekend"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CuddlyNest Search & Listings — MCP Server
A Model Context Protocol (MCP) server for searching CuddlyNest hotels and retrieving listing details, including room options, prices, availability and cancellation policies.
Read-only by default: search and listing details only. No booking, no payment.
Booking steps exist behind CUDDLYNEST_ENABLE_BOOKING_TOOLS=true (off by default);
they never take card data, payment happens on CuddlyNest's checkout.
How it gets the data
This server reads that data the same way a visitor does: it opens the real, public listing page in a headless browser (Playwright/Chromium), lets the page's own JavaScript load the rooms, waits for them to render, and reads the result out of the DOM.
Data | Source |
Name, description, address, coordinates, star rating, amenities, images | Listing page |
Room title, partner, | Rendered listing page DOM, via a React-fiber walk ( |
Destination → place candidates + top hotels |
|
Destination → broader city hotel list (~60–250) |
|
|
|
|
|
The DOM extraction, and how it breaks
extractRoomsFromDom() walks every price-shaped text node (COL$742,637), then
walks up its React fiber tree to the nearest ancestor component whose props
carry both unit_price and roomGroups. Those props are the room offer the
page already rendered.
With CUDDLYNEST_LDP_ROOMS_URL and the JWT credentials set, room prices come
instead from the listing page's own room-groups socket (ldp-rooms.ts): the same
data in 1–6 s, no browser. The page scrape stays the default and the fallback
(rooms.source says which one answered).
This is coupled to CuddlyNest's current frontend internals (a React prop shape,
not a stable contract). If they ship a frontend change it can start returning
zero rooms even though the public page still shows prices. The single place to
update is the detector condition 'unit_price' in p && 'roomGroups' in p in
scrape-listing.ts. npm run e2e:sansiraka is meant to
catch that early (non-zero exit, not a silent empty result).
The fromPriceText ("From COL$…") field uses a looser heuristic and can come
back null even on a healthy scrape; rooms.fromPrice (cheapest extracted
unit) is the reliable figure.
Related MCP server: MAQAMI Travel
Requirements
Node.js 18+
A Chromium build for Playwright.
npm installrunsplaywright install chromiumautomatically (postinstall); if that is blocked in your environment, runnpx playwright install chromiumonce by hand.
Installation
Published as cuddlynest-mcp on
npm and listed in the official MCP registry
as io.github.mafedelahoz/cuddlynest-mcp.
{
"mcpServers": {
"cuddlynest": {
"command": "npx",
"args": ["-y", "cuddlynest-mcp"]
}
}
}Add "--ignore-robots-txt" to args to bypass robots.txt for the
listing-page fetches. CUDDLYNEST_SCRAPE_TIMEOUT_MS (default 35000) caps how
long the browser waits for prices to render.
An MCPB bundle (.mcpb) for Claude Desktop is attached to each
GitHub release — note it
does not bundle Chromium, so run npx playwright install chromium once after
installing it that way.
Remote / Streamable HTTP
Default transport is stdio. For a hosted deployment, run it over Streamable HTTP:
node dist/index.js --http 8080 # or: MCP_TRANSPORT=http PORT=8080 node dist/index.js
# POST http://<host>:8080/mcp — JSON-RPC (stateless, no sessions)
# GET http://<host>:8080/health — livenessTools
Both tools are annotated readOnlyHint: true — they never write, book, or pay.
cuddlynest_search
Search stays, attractions or flights for a destination. vertical picks what to
search and source picks where the data comes from.
Parameter | Required | Description |
| yes | City / area string, e.g. |
| no |
|
| no |
|
| no | Max results (default 20 for stays/attractions, 10 for flights; max 50) |
| flights | Departure city or IATA code, e.g. |
| no | Flights: |
| live stays, flights |
|
| no | Guests / passengers. Flights need |
| no | Stays from the public-site fallback only |
Sources
| Stays | Attractions | Flights |
| Catalog DB (cached per destination); falls back to the public site if the DB fails, has no results or the destination is ambiguous | Cache of earlier live searches (24 h, refreshed in the background in HTTP mode) | Cache of earlier live searches (30 min, indicative fares) |
| Catalog DB only; an error instead of a fallback | same as | same as |
| Real-time availability with prices (needs dates) | Tours and activities with a from-price | Real-time fares |
live calls CuddlyNest's real-time APIs, which reach travel suppliers, so it is
only used when a caller asks for it explicitly and never as an automatic
fallback. Attractions and flights have no catalog database (their inventory
comes from suppliers), so auto / db answer from a cache of earlier live
searches and never call the API; a cache miss answers source: "unavailable"
with reason: "<vertical>_not_cached". Cached results carry cachedAt. A failed live search returns an error with liveErrorCode; it never
falls back to another source.
Returns (all verticals share the same static shape, and prices only ever
appear under each result's pricing):
Stays:
stays[]withid,type,name,slug,category,location { city, country, lat, lng, nearest_airport },tags,description_short,amenities,rating(/10),cover_image_url,url; live results adddetails(neighborhood, distance, reviews, nearby places) andpricing.Attractions:
attractions[]with the same static fields plusduration,rating(/5),details(reviews, sub-categories, languages, accessibility) andpricing(from-price, currency, availability, priced date).Flights:
flights[]withlegs[](airports, local times, duration, stops,segments[]with carrier and flight number),airlines,baggage,conditions(refundable / changeable) andpricing(total, base, taxes, per passenger, price guarantee expiry), plus the searchsessionId.vertical/sourcecombinations with no data source answersource: "unavailable"with areasonand emptyresults.
cuddlynest_listing_details
Static basics and rooms/pricing for one hotel.
Parameter | Required | Description |
| yes | Listing URL or numeric |
| for pricing |
|
| no | defaults 2 / 0 / – / 0 / 1 |
| no | ISO 4217, default |
| no | ignore robots.txt for the static fetch |
Returns: { productId, hotelUrl, guests, staticListing, staticError, rooms, roomsError, notes }.
rooms.units[] is the extracted room offers, each with title, partnerName,
unitPrice, currency, remainingRooms, guests, cancellationPolicyType,
cancellationPolicyText, priceBreakdown, roomFilters. rooms also carries
fromPrice, partnersSeen, listingUrl, scrapedAt. With the booking tools
enabled, each unit adds bookingOptions[] (one per rate: meal plan and
cancellation type, price, and the offer ids cuddlynest_booking_checkout takes).
Development
npm install # installs deps + Chromium (postinstall)
npm run build # sync-version + tsc -> dist/
npm run typecheck
npm test # offline: smoke test (stdio) + scraper tests
npm run e2e:sansiraka # ONLINE: real scrape of cuddlynest.com, structural asserts
npm run watchArchitecture
index.ts— MCP server, tool schemas, stdio and Streamable HTTP transports,robots.txthandlingcuddlynest.ts— hotel-URL parsing, static-listingld+jsonparse, destination autosuggestion, result shapingscrape-listing.ts—resolveListingPath,buildListingUrl,scrapeListing(headless browser),extractRoomsFromDom(React-fiber walk)util.ts— generic object/JSON helpersdb.ts,cache.ts,destination.ts— read-only catalog DB for stays, the JSON caches (stays, attractions, flights) with age-based expiry, and destination parsingfallback-provider.ts— public-site fallback forsource: "auto"ldp-rooms.ts— room prices from the listing page's room-groups socket (opt-in, falls back to the page scrape)auth.ts— service JWT (fetched with an API key, cached, renewed before expiry)be-api-provider.ts— live stays availability (source: "live")attractions-provider.ts,flights-provider.ts— live attractions and flights searchbooking.ts— stays booking: a room rate → Request to Book → CuddlyNest checkout link with the final price and cancellation policy; the user pays on the checkout page. Booking status by enquiry id + booking number. Hidden unlessCUDDLYNEST_ENABLE_BOOKING_TOOLS=trueattractions-booking.ts,flights-booking.ts— attraction options → live availability (with the CuddlyNest checkout link where the user pays) → checkout preview, and flight live price → pending booking, behind the same flag. Flights has no hand-off yet: the site's flights checkout isn't enabled
License
MIT — see LICENSE.
Available Tools
2 toolscuddlynest_listing_detailsGet CuddlyNest hotel rooms & pricesARead-only
Get details for a specific CuddlyNest hotel: static basics (name, location, description, amenities, images) from the listing page, plus room options, prices, availability and cancellation policies read from the public listing page rendered in a headless browser.
Inputs: hotel (required), rooms, adults, checkin, +6 more.
cuddlynest_searchSearch CuddlyNest hotelsARead-only
Search CuddlyNest for a destination and the top hotels there. Returns place candidates (city/region + coordinates + total property count) and a list of hotels — name, listing URL, star + guest rating, and (when available) images, distance from the centre and key amenities. Pass a hotel's product_id from the results to cuddlynest_listing_details for live rooms and prices. The hotel list is top-matches scale (~10-60), not the full inventory.
Inputs: destination (required), rooms, adults, checkin, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools occupy completely separated stages of the workflow: search discovers destinations and top hotels, while listing_details drills into one hotel using a product_id. There is no overlap in purpose or output.
Both names share a cuddlynest_ prefix, making the server's brand clear, but one uses an imperative verb (search) while the other is a noun phrase (listing_details). This minor inconsistency prevents a perfect score.
Two tools is borderline for a typical MCP server, though the count fits the narrow search-and-details purpose. It feels slightly thin because there is no tool for direct lookups or other listing workflows.
The described lifecycle is complete: cuddlynest_search produces both destination candidates and hotels with product IDs, and cuddlynest_listing_details consumes those IDs to return live rooms, prices, and policy details. No obvious dead end exists in the intended flow.
Maintenance
Related MCP Connectors
Live hotel search and booking for AI agents in DACH, the UK and 10 US cities.
Search and book 3M+ hotels in 200+ countries. Agents pay per reservation in USDC on Base over x402. Hosted, no auth.
Search and book hotels, shorten or cancel stays, and check support cases in Engine.
AI hotel search and booking: millions of properties, 85,000+ cities, live rates.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search, browse, and book hotels from a database of 2 million properties worldwide. Provides comprehensive hotel search capabilities with location lookup, filtering by amenities, detailed property information, and integrated booking functionality.61ISC
- AlicenseBqualityBmaintenanceOfficial MCP server for MAQAMI, a hotel and flight booking platform with 3M+ hotels. Search live hotel rates and flights, look up places, airports and hotel details, then prebook and book. Remote Streamable HTTP endpoint, no API key required.4158 npm2MIT

Dida Hotel MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to search and book hotels globally with real-time pricing and inventory from over 2 million properties.46MIT- AlicenseNot gradedqualityBmaintenanceEnables searching Booking.com accommodations by destination, dates, and party size, and retrieving full property details such as pricing, policies, ratings, photos, and available room suites as JSON.312 npmMIT