MCP Server Airbnb

What openbnb-org/mcp-server-airbnb MCP server does

The openbnb-org/mcp-server-airbnb MCP server exposes two tools for working with Airbnb listing data. airbnb_search finds properties based on a required location and optional travel, guest, price, property, and pagination parameters. airbnb_listing_details retrieves information for a specified Airbnb listing ID.

Search results include property information, pricing, pagination data, and a URL for reference. Listing details can include coordinates, neighborhood information, amenities, house rules, policies, highlights, descriptions, and a direct Airbnb link.

How it works

The server uses the Model Context Protocol over stdio and runs on Node.js 18 or newer. Searches normally send requests to Airbnb. When a search provides a location string without a Google Maps Place ID, the server first uses Photon for geocoding and can fall back to Nominatim if Photon does not provide a bounding box. Supplying placeId skips those geocoding requests and takes precedence over the text location.

The openbnb-org/mcp-server-airbnb MCP server sends only the entered location string to the geocoding services. The documentation describes rate-limit awareness, request timeouts, error logging, and robots.txt handling, including an option to override robots.txt restrictions.

Setup and configuration

For Claude Desktop, install the .mcpb file from a project release and configure its extension settings. The repository also documents npm-based setup for clients such as Cursor. The local command uses Node.js and runs the package as an stdio process:

{
  "mcpServers": {
    "airbnb": {
      "command": "npx",
      "args": ["-y", "@openbnb/mcp-server-airbnb"]
    }
  }
}

The --ignore-robots-txt argument can be added when the client must bypass robots.txt restrictions. The documented recommendation is to leave this disabled except when testing requires it.

DISABLE_GEOCODING disables Photon and Nominatim calls and lets Airbnb resolve the location. Its default is false. With geocoding disabled, non-US location searches may produce inaccurate results. An explicit placeId is another way to avoid third-party geocoding without disabling location resolution globally.

Tools and capabilities

• Search by city, state, region, or other location text.
• Target a location with a Google Maps Place ID.
• Filter by check-in and check-out dates.
• Set adults, children, infants, and pets.
• Apply minimum and maximum nightly prices.
• Filter for entire homes, private rooms, shared rooms, or hotel rooms.
• Continue through results with a pagination cursor.
• Retrieve listing amenities, including categories for items not included at the property.
• Override robots.txt behavior per request through the tool parameters.

Limitations and notes

The openbnb-org/mcp-server-airbnb MCP server depends on Airbnb responses and external geocoding services for searches that do not include a Place ID. Nominatim has a documented usage limit of approximately one request per second. Disabling geocoding can affect the accuracy of non-US searches.

The material does not identify an API key requirement, OAuth flow, booking support, or a license. The hosted openbnb.ai service is described as a separate alternative and is not the local server documented here.