Ripe MCP Server

Give AI assistants, chatbots, and applications direct, structured access to real-time lodging, content, and availability, all while respecting your commission structure and goals.

Why we built an MCP

Travelers increasingly start their trip planning in a conversation, not a search bar — asking an AI assistant where to stay, what's nearby, and whether it's actually available, instead of browsing a website. The Ripe MCP Server meets that shift head-on.

It exposes Ripe's lodging search, property content, and live availability through the Model Context Protocol (MCP) — an open standard that lets AI assistants and agent frameworks query external data sources the same, predictable way, without a bespoke integration for every platform. Connect once, and any MCP-compatible assistant can ask Ripe real questions and get back live, structured, trustworthy answers.

📘
New to MCP?
Model Context Protocol is an open standard for connecting AI applications to external tools and data. If your assistant or agent framework already supports MCP, connecting to Ripe is a matter of pointing it at one URL — see Getting Started below.

Why you might build on the Ripe MCP Server

Reach travelers wherever they're already planning. Your lodging data becomes queryable by any AI assistant or travel agent your users are already talking to — without asking travelers to visit a specific site first.
Structured, LLM-ready responses. Every tool returns clean, predictable JSON built for language models to reason over — no scraping, no fragile parsing of HTML or free text.
Live, accurate availability. Search results are useful for comparison, but every property's real price and bookability is confirmed live at query time — so what an assistant tells a traveler matches what they'll see at checkout.
Self-describing tools. Each capability documents its own inputs and outputs, so an AI assistant (or a developer) can discover what's available without reading a separate integration guide line by line.
Built to evolve without breaking you. The API is versioned from the start, so new capability gets added without disrupting existing integrations.
Nothing to build to get started. No account setup, no credentials, no approval flow — point your client at the URL and start querying (see What's Coming for upcoming changes).

MCP vs. the Ripe REST API — which should you use?

Both run on the same underlying lodging data. The right choice depends on what you're building.

	Ripe REST API	Ripe MCP Server
Best for	Custom applications — booking engines, dashboards, internal tools	AI assistants, chatbots, and autonomous agents
Consumer	Your own code, calling specific endpoints you choose	An LLM, discovering and calling tools on its own
Integration effort	You design the request/response handling per use case	Self-describing — the assistant reads tool definitions and figures out the calls
Scope today	Full read access, with transactional capability	Read-only: search, content, and availability
Typical use case	"Build our booking flow" or "power our internal reporting"	"Let an AI assistant answer trip-planning questions with live data"

In short: if you're building a product a person clicks through, use the REST API. If you're building something an AI assistant or agent talks to on a traveler's behalf, use MCP. Many integrations end up using both, side by side, against the same underlying data.

What you can query

The MCP server exposes five read-only tools. An AI assistant calls whichever it needs, in whatever order the conversation calls for.

Tool	What it returns
`list_destinations`	The directory of active destinations available to search, with location metadata — useful for narrowing a broad or vague request
`search_properties`	Properties matching a place, date range, budget, amenities, rating, or free-text "vibe" description (e.g., "cozy," "walkable," "ski-in/ski-out")
`get_property_content`	Descriptive details for specific properties — photos, amenities, address, and review summaries
`get_property_availability`	Live, confirmed pricing and bookability for one property over a specific stay window
`list_search_vocabulary`	The exact amenity and property-type vocabulary the search recognizes, for precise filtering

👍
A note on accuracy
search_properties is optimized for fast comparison across many options and may return an indicative rate. For a rate and availability you can act on, always confirm with get_property_availability before presenting it as bookable — this is true whether you're a person or an AI.

Getting started

This will be added and updated as the MCP is made available.

A simple flow to try first:

Ask your assistant something like: "Find a pet-friendly place to stay near Sandy Cove next weekend, under $250 a night."
It should call search_properties with a location, dates, a price ceiling, and the "Pets allowed" amenity.
For a top candidate, it should follow up with get_property_availability to confirm the real price and bookability before answering you.
The response should include a direct link back to the live booking page to complete a reservation.

What's coming

🚧
Authentication is coming soon
The MCP server is public and unauthenticated today. We'll soon be introducing basic ID-based authentication to access the server. Existing integrations will get advance notice before this takes effect, and the change is designed to be lightweight — a straightforward addition to your connection, not a rebuild of your integration.

We're also expanding the toolset over time, including deeper content coverage and, longer term, moving beyond search and information into full booking. If you're building something today, design for read-only, informational use — anything transactional should go through the REST API in the meantime.

FAQ

Is there a cost to use this?
No — the MCP server is free to connect to today. In there future, there could be a charge introduced for higher limits and/or functionality.

Which AI assistants or frameworks does this work with?
Any client or framework that supports the Model Context Protocol, including Claude and CLI, AI chat bots, along with most agent frameworks that support remote MCP servers.

Can I book a reservation directly through the MCP server?
Not yet. It's read-only today — search, content, and availability. Every response includes a link to complete a booking on the live site.

How fresh is the data?
Search and content results are served efficiently, but pricing and availability are always confirmed live at query time — never from a cache.

Where do I ask questions or report an issue?
Reach out to your Ripe account team, or contact us through the developer support channel linked at the top of this hub.

This page describes the current, publicly accessible Ripe MCP Server. Capabilities and authentication requirements will evolve — check back here for the latest.