Claude Code

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

\n\n

Claude Desktop

\n\nSettings, then Connectors, then Add custom connector, then paste `https://mcp.hasdata.com/api/mcp?apis=airbnb` and sign in.\n\nFor the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The `@hasdata/airbnb-mcp` package is that launcher, and it reads the key from the environment. Add this to `claude_desktop_config.json`:\n\n```json\n{\n \"mcpServers\": {\n \"airbnb\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"@hasdata/airbnb-mcp\"],\n \"env\": { \"HASDATA_API_KEY\": \"YOUR_KEY\" }\n }\n }\n}\n```\n\nFor Python instead of Node, swap the launcher for the PyPI package, which `uvx` runs without a manual install:\n\n```json\n{\n \"mcpServers\": {\n \"airbnb\": {\n \"command\": \"uvx\",\n \"args\": [\"hasdata-airbnb-mcp\"],\n \"env\": { \"HASDATA_API_KEY\": \"YOUR_KEY\" }\n }\n }\n}\n```\n\n

\n\n

Cursor

\n\n`~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one:\n\n```json\n{\n \"mcpServers\": {\n \"airbnb\": {\n \"url\": \"https://mcp.hasdata.com/api/mcp?apis=airbnb\",\n \"headers\": { \"x-api-key\": \"HASDATA_API_KEY\" }\n }\n }\n}\n```\n\n

\n\n

Windsurf

\n\n`~/.codeium/windsurf/mcp_config.json`. Windsurf calls the field `serverUrl`, not `url`:\n\n```json\n{\n \"mcpServers\": {\n \"airbnb\": {\n \"serverUrl\": \"https://mcp.hasdata.com/api/mcp?apis=airbnb\",\n \"headers\": { \"x-api-key\": \"HASDATA_API_KEY\" }\n }\n }\n}\n```\n\n

\n\n

VS Code

\n\n`.vscode/mcp.json` in the workspace:\n\n```json\n{\n \"servers\": {\n \"airbnb\": {\n \"type\": \"http\",\n \"url\": \"https://mcp.hasdata.com/api/mcp?apis=airbnb\",\n \"headers\": { \"x-api-key\": \"HASDATA_API_KEY\" }\n }\n }\n}\n```\n\n

\n\n## Example prompts\n\nPrompts, 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 5 credits.\n\n> Search Austin stays for two adults from September 15 to 18 and give me the ten highest-rated under $200 a night.\n\n*One call, 5 credits. Rating and nightly price come back on the search result.*\n\n> Take the top result and pull its full amenities, the guest and bedroom count, and the host details.\n\n*One call, 5 credits. Those live on the property page, which the details tool reads by URL.*\n\n> Compare the nightly price of a three-night stay for two guests in Austin against Nashville.\n\n*Two calls, 10 credits, one search per city.*\n\n> For this listing URL, tell me how many beds and baths it has and whether the host is a Superhost.\n\n*One call, 5 credits.*\n\nA 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.\n\n## Tools\n\nTwo 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.\n\nThe 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.\n\n### Get Airbnb listings\n\n[`hasdata_airbnb_listing_getAirbnbListings`](https://docs.hasdata.com/apis/airbnb/listing?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp)\n\nA page of search results by location and dates.\n\n| Parameter | Type | Required | Notes |\n| :--- | :--- | :--- | :--- |\n| `location` | string | yes | The place to search, such as `Austin, Texas` |\n| `checkIn` | string | yes | Check-in date, `YYYY-MM-DD` |\n| `checkOut` | string | | Check-out date, `YYYY-MM-DD` |\n| `adults` / `children` / `infants` / `pets` | number | | Guest composition, each a count |\n| `nextPageToken` | string | | The `pagination.nextPageToken` from the previous response |\n\nReturns 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`.\n\n> 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.\n\n```json\n{\n \"id\": \"17545365\",\n \"url\": \"https://www.airbnb.com/rooms/17545365\",\n \"title\": \"Home in East Austin\",\n \"latitude\": 30.25741,\n \"longitude\": -97.73366,\n \"description\": \"Downtown Casa - neighborhood feel, close to it all\",\n \"rating\": 4.87,\n \"reviews\": 601,\n \"badges\": [\"Guest favorite\"],\n \"price\": {\n \"originalPrice\": \"$607\",\n \"discountedPrice\": \"$447\",\n \"qualifier\": \"for 3 nights\",\n \"breakdown\": [{ \"description\": \"3 nights x $149.00\", \"price\": \"$447.00\" }]\n }\n}\n```\n\n### Get Airbnb property details\n\n[`hasdata_airbnb_property_getAirbnbPropertyDetails`](https://docs.hasdata.com/apis/airbnb/property?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp)\n\nOne listing in full, by its URL.\n\n| Parameter | Type | Required | Notes |\n| :--- | :--- | :--- | :--- |\n| `url` | string | yes | An Airbnb listing URL, the `url` field from a search result |\n\nReturns `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.\n\n```json\n{\n \"id\": \"17545365\",\n \"title\": \"Downtown Casa - neighborhood feel, close to it all\",\n \"overview\": [\"4 guests\", \"2 bedrooms\", \"2 beds\", \"2 baths\"],\n \"rating\": 4.87,\n \"reviews\": 601,\n \"address\": \"Austin, Texas, United States\",\n \"guestCapacity\": 4,\n \"host\": { \"name\": \"Deanna\", \"isSuperhost\": true, \"isVerified\": true, \"reviews\": 1273, \"rating\": 4.86, \"yearsHosting\": 11 },\n \"amenities\": [\n { \"title\": \"Wifi\", \"type\": \"SYSTEM_WI_FI\", \"available\": true },\n { \"title\": \"Free washer – In unit\", \"type\": \"SYSTEM_WASHER\", \"available\": true }\n ]\n}\n```\n\n## Errors and failure paths\n\nYour 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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\n**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.\n\nResults that carry data also carry a `requestMetadata.id` worth quoting in support.\n\n## Pricing, free tier and limits\n\nEach Airbnb tool costs **5 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.\n\nThe free trial is **1,000 credits over 30 days with no card**, which is 200 Airbnb calls. After that an active account keeps getting 100 credits topped up each day whenever its balance drops below 100, so a low-volume agent runs on the free tier indefinitely.\n\nPaid plans start at **$49 a month** for 200,000 credits, which is 40,000 calls. The unit price falls with volume, from **$1.23 per 1,000 calls** on the entry plan to **$0.50** on Business, **$0.42** on Growth and **$0.37** on the largest [high-volume plans](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp).\n\nYour plan also sets concurrency. The free trial allows 1 request at a time, Startup 15, Business 30, Growth 50, and the high-volume plans run from 200 to 1,500. Handle the overflow case defensively in anything unattended.\n\nA request that comes back non-200 is not billed. A successful call that finds nothing is still a call.\n\n## Tool selection\n\nThe `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.\n\n```\n?apis=airbnb the two tools in this repo\n?apis=airbnb,booking add Booking.com stays\n?apis=airbnb,google_maps add Google Maps places\n```\n\nThe 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.\n\n## How it compares\n\nAirbnb 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.\n\n| | Airbnb partner API | This server |\n| :--- | :--- | :--- |\n| Purpose | Manage your own listings | Read the public market |\n| Access | Partner approval | One key and one URL |\n| Search across the market | No | Yes |\n| Setup | Business onboarding | None |\n| Output | Partner payloads | Structured JSON, price and rating pre-parsed |\n\n**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.\n\n## FAQ\n\n### Is there an official Airbnb MCP server?\n\nAirbnb does not publish one. This one is maintained by HasData and reads public pages, which is why it needs no Airbnb developer account.\n\n### What is an Airbnb MCP server?\n\nA 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.\n\n### Do I need an Airbnb API key or partner account?\n\nNo. The only credential is your HasData key. There is no partner onboarding, because the tools read public Airbnb pages.\n\n### Why does the search result not show beds or amenities?\n\nBecause 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.\n\n### Can I filter by guests, pets or dates?\n\nYes. The listing tool takes `checkIn`, `checkOut` and the `adults`, `children`, `infants` and `pets` counts, and returns availability and pricing for that party and window.\n\n### Can I use this together with other HasData APIs?\n\nYes. The `apis` parameter takes a list, and `?apis=airbnb,booking` gives your agent Airbnb plus Booking.com. [Drop the parameter](#tool-selection) and you get everything.\n\n### Compliance and personal data\n\nHasData 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.\n\n## HasData links\n\n| | |\n| :--- | :--- |\n| Product page and request builder | [Airbnb Scraper API](https://hasdata.com/apis/airbnb-api?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| Server documentation | [MCP server docs](https://docs.hasdata.com/mcp-server?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| All 57 tools in one server | [HasData/hasdata-mcp](https://github.com/HasData/hasdata-mcp) |\n| Client walkthroughs | [MCP clients and integrations](https://hasdata.com/integrations/mcp?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| Everything else we scrape | [Airbnb Scraper API and 54 more](https://hasdata.com/apis/?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| Plans and credit costs | [Plans and credit costs](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| Keys and usage | [HasData dashboard](https://app.hasdata.com?utm_source=github&utm_medium=syndication&utm_campaign=airbnb-mcp) |\n| Node launcher on npm | [@hasdata/airbnb-mcp](https://www.npmjs.com/package/@hasdata/airbnb-mcp) |\n| Python launcher on PyPI | [hasdata-airbnb-mcp](https://pypi.org/project/hasdata-airbnb-mcp/) |\n\n## Development\n\nThis repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.\n\nThe 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 5 credits, which is the price of a canary that can fail for the right reason.\n\n```bash\n# macOS and Linux\nHASDATA_API_KEY=your_key_here npm test\n\n# Windows PowerShell\n$env:HASDATA_API_KEY=\"your_key_here\"; npm test\n```\n\nThe 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.\n\n## Contributing\n\nCorrections 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.\n\n## License\n\nMIT. See [LICENSE](https://github.com/HasData/airbnb-mcp/blob/main/LICENSE).\n","changelogMarkdown","videoKey","requiredSecretsJson","[{\"name\":\"x-api-key\",\"scope\":\"per-user\",\"header\":\"x-api-key\"}]","publishedAt","priceCents","trialDays",0,"upstream",{"_116":117,"_118":119,"_120":121,"_122":123,"_124":125,"_126":127},"requiredSecrets",[110],"tags",[99,100,101,102,19,103,104,105,106,107,108,109],"assets",[],"stats",{"_97":86,"_98":86},"ratingAvg","reviewCount","ai-agents","airbnb","claude","cursor","llm-tools","real-estate","short-term-rental","travel","vacation-rental","web-scraping","windsurf",{"_111":112,"_113":114,"_115":112},"name","x-api-key","scope","per-user","header","topics",[99,100,101,102,19,103,135,136,137,104,105,106,107,108,109],"license","MIT","language","JavaScript","registryName","com.hasdata/airbnb","homepage","https://hasdata.com/apis/airbnb-api","packages",[128,129],{"_130":134,"_132":22,"_75":76},{"_130":131,"_132":133,"_75":76},"registryType","pypi","identifier","hasdata-airbnb-mcp","npm","mcp","mcp-server","model-context-protocol","ENV",{"_140":141,"_142":143,"_144":145},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]

HasData Airbnb