HasData Airbnb

Airbnb MCP Server

A hosted Airbnb MCP server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Airbnb tools. Search stays by place name or map area, and read a single listing in full, all as structured JSON, with no Airbnb developer account and no partner approval.

It reads public listing pages that a signed-out visitor can see.

1,000 free credits every month, no card required, which is 100 Airbnb calls.

https://mcp.hasdata.com/mcp?apis=airbnb

[Glama score] [tool contract] [MCP] [Tools] [npm] [PyPI] [License]

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• Tool selection
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Airbnb developer account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/airbnb-mcp on npm and hasdata-airbnb-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

claude mcp add --transport http airbnb "https://mcp.hasdata.com/mcp?apis=airbnb" \  --header "x-api-key: HASDATA_API_KEY"

{  "mcpServers": {    "airbnb": {      "command": "npx",      "args": ["-y", "@hasdata/airbnb-mcp"],      "env": { "HASDATA_API_KEY": "YOUR_KEY" }    }  }}

{  "mcpServers": {    "airbnb": {      "command": "uvx",      "args": ["hasdata-airbnb-mcp"],      "env": { "HASDATA_API_KEY": "YOUR_KEY" }    }  }}

{  "mcpServers": {    "airbnb": {      "url": "https://mcp.hasdata.com/mcp?apis=airbnb",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

{  "mcpServers": {    "airbnb": {      "serverUrl": "https://mcp.hasdata.com/mcp?apis=airbnb",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

{  "servers": {    "airbnb": {      "type": "http",      "url": "https://mcp.hasdata.com/mcp?apis=airbnb",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 10 credits.

Search Austin stays for two adults from September 15 to 18 and give me the ten highest-rated under $200 a night.

One call, 10 credits. Rating and nightly price come back on the search result.

Take the top result and pull its full amenities, the guest and bedroom count, and the host details.

One call, 10 credits. Those live on the property page, which the details tool reads by URL.

Compare the nightly price of a three-night stay for two guests in Austin against Nashville.

Two calls, 20 credits, one search per city.

For this listing URL, tell me how many beds and baths it has and whether the host is a Superhost.

One call, 10 credits.

A search result is deliberately light, enough to rank and shortlist. The amenities, beds, host and full description come from the property call, so a prompt that shortlists then inspects three homes is one search plus three property calls.

Tools

Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as Airbnb updates. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.

The samples are the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.

Get Airbnb listings

hasdata_airbnb_listing_getAirbnbListings

A page of search results by place name and dates, or by a map area.

checkIn is always required. Beyond it the tool takes either a location or a full map bounding box, and a box counts only when all four corners are present. Three of the four fail with requiredIfExistsAny on the missing one. A box searches an area Airbnb has no name for, which a place name cannot express.

Returns a properties array and pagination, whose nextPageToken and pageTokens walk the result set. Each property carries id, url, title, latitude, longitude, a short description tagline, a photos array, rating, reviews, a badges array such as Guest favorite or Superhost, and a price object. price holds originalPrice, an optional discountedPrice when the stay is discounted, a qualifier like for 3 nights, and a breakdown.

A search result is intentionally light. Beds, baths, amenities, the host and the full description are not here, they come from the property tool below. Do not expect a bedroom count on a search result.

{  "id": "17545365",  "url": "https://www.airbnb.com/rooms/17545365",  "title": "Home in East Austin",  "latitude": 30.25741,  "longitude": -97.73366,  "description": "Downtown Casa - neighborhood feel, close to it all",  "rating": 4.87,  "reviews": 601,  "badges": ["Guest favorite"],  "price": {    "originalPrice": "$607",    "discountedPrice": "$447",    "qualifier": "for 3 nights",    "breakdown": [{ "description": "3 nights x $149.00", "price": "$447.00" }]  }}

Get Airbnb property details

hasdata_airbnb_property_getAirbnbPropertyDetails

One listing in full, by its URL.

Returns title, an overview array like ["4 guests", "2 bedrooms", "2 beds", "2 baths"], the full description, rating, reviews, address, latitude, longitude, a photos array, guestCapacity, a host object, an amenities array, and safetyAndPropertyInfo. The host object carries name, isSuperhost, isVerified, the host's own reviews, rating and yearsHosting. Each amenity carries a title, a type, an optional description and an available flag, so a filter reads available, it does not assume every listed amenity is present.

{  "id": "17545365",  "title": "Downtown Casa - neighborhood feel, close to it all",  "overview": ["4 guests", "2 bedrooms", "2 beds", "2 baths"],  "rating": 4.87,  "reviews": 601,  "address": "Austin, Texas, United States",  "guestCapacity": 4,  "host": { "name": "Deanna", "isSuperhost": true, "isVerified": true, "reviews": 1273, "rating": 4.86, "yearsHosting": 11 },  "amenities": [    { "title": "Wifi", "type": "SYSTEM_WI_FI", "available": true },    { "title": "Free washer – In unit", "type": "SYSTEM_WASHER", "available": true }  ]}

Errors and failure paths

Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with isError set to true and the reason as text. The agent reads a message where you might expect a status line.

A wrong key surfaces as tool output, not as a failed connection. tools/list accepts any non-empty key and returns both tools, so the client completes its handshake and shows green. The first tool call then comes back with isError: true and the text HasData API error: 401 Unauthorized. Watch for that string, because nothing earlier in the flow reports the problem.

A missing key is the one real HTTP error. Authorization runs before any tool, and the connection itself fails with 401. CORS headers are present, and a browser client reads the status and not an opaque network failure.

An argument that breaks a tool's schema is rejected before it becomes a scrape. The server answers with isError: true and the text MCP error -32602: Input validation error, naming the offending field. Nothing is fetched and nothing is charged.

A search with no availability returns a successful result with an empty properties array, not an error. A location and date range with nothing open still comes back with requestMetadata.status set to ok. Test for the array length before you iterate.

A listing that has been removed returns 400 with requestMetadata.status set to error. A URL from an old search can point at a home that is gone.

Results that carry data also carry a requestMetadata.id worth quoting in support.

Pricing, free tier and limits

Each Airbnb tool costs 10 credits per successful call. Response size does not change the price. A search page with dozens of stays costs the same as one with two.

The free tier is 1,000 credits every month with no card, which is 100 Airbnb calls. It renews with the billing cycle, so a low-volume agent runs on the free tier indefinitely.

Paid plans start at $59 a month for 200,000 credits, which is 20,000 calls. The unit price falls with volume, from $1.48 per 1,000 calls on the entry plan to $0.60 on Basic and $0.41 across the Growth tiers. Current figures live on the pricing page.

Your plan also sets concurrency. The free tier allows 5 requests at a time, Startup 5, Basic 15, and the Growth tiers run from 50 to 500. Handle the overflow case defensively in anything unattended.

A request that comes back non-200 is not billed. A successful call that finds nothing is still a call.

Tool selection

The apis query parameter decides which tools your agent sees. Fewer tools means less context spent on tool definitions, and fewer chances for the model to reach for the wrong one.

?apis=airbnb                     the two tools in this repo?apis=airbnb,booking             add Booking.com stays?apis=airbnb,google_maps         add Google Maps places

The parameter takes provider names like airbnb and individual API names like airbnb_listing. Misspelled names are ignored. If every name is wrong the request fails with 400, and the body lists both what it did not recognise and every valid value. Drop the parameter and the same endpoint exposes all 57 HasData tools.

How it compares

Airbnb has no public search API. Its API program is a partner and co-host integration for managing your own listings, not a way to read the market. For searching stays and reading arbitrary listings, scraping the public pages is the only route, and this server does that behind a stable schema.

What this server does not do. No booking, no messaging, no host dashboard, no guest data. It reads what a signed-out visitor can see.

FAQ

Is there an official Airbnb MCP server?

Airbnb does not publish one. This one is maintained by HasData and reads public pages, which is why it needs no Airbnb developer account.

What is an Airbnb MCP server?

A server that exposes Airbnb data as tools an AI client can call. The client sends a tool call over the Model Context Protocol, the server fetches the data and returns structured JSON, and the model works with the result. This one exposes two tools and runs remotely.

Do I need an Airbnb API key or partner account?

No. The only credential is your HasData key. There is no partner onboarding, because the tools read public Airbnb pages.

Why does the search result not show beds or amenities?

Because Airbnb does not put them on the search card. They live on the property page, which the details tool reads by URL. Search to shortlist, then call the property tool for depth.

Can I filter by guests, pets or dates?

Yes. The listing tool takes checkIn, checkOut and the adults, children, infants and pets counts, and returns availability and pricing for that party and window.

Can I use this together with other HasData APIs?

Yes. The apis parameter takes a list, and ?apis=airbnb,booking gives your agent Airbnb plus Booking.com. Drop the parameter and you get everything.

Compliance and personal data

HasData accesses publicly available data only. A platform's terms may restrict automated access, and you are responsible for your own compliance. Where the data you collect includes personal information, make sure you have a lawful basis for it under GDPR, CCPA or the equivalent rules in your jurisdiction.

HasData links

Development

This repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.

The tests in test/ assert the tool contract, the part that can break without a commit here. They check that ?apis=airbnb returns exactly two tools, that every tool still declares its required parameters, that no name changed, and that the key in use is actually accepted. That last check calls a tool for real and costs 10 credits, which is the price of a canary that can fail for the right reason.

# macOS and LinuxHASDATA_API_KEY=your_key_here npm test
# Windows PowerShell$env:HASDATA_API_KEY="your_key_here"; npm test

The same suite runs in CI on every push and once a week on a schedule, because the upstream tool list can change without anyone touching this repository. A failure means the tool list moved, the key stopped working, or the endpoint was unreachable, and the assertion message says which.

Contributing

Corrections to the tool tables and the response samples are the most useful contribution, because those are the parts that drift. Include the call you made and the response you got. Pull requests from forks run the suite without a key, and the live checks skip instead of going red.

License

MIT. See LICENSE.