Airbnb

Created By
openbnb-orga year ago
MCP Server for searching Airbnb and get listing details.
Overview

What is Airbnb MCP Server?

The Airbnb MCP Server is a tool designed for searching Airbnb listings and retrieving detailed information about them.

How to use Airbnb MCP Server?

To use the Airbnb MCP Server, you can either install it on your local machine using Node.js or set it up via Smithery. You can search for listings by providing various filters such as location, check-in and check-out dates, and number of guests.

Key features of Airbnb MCP Server?

  • Search for Airbnb listings with various filters.
  • Get detailed information about specific listings.
  • Respects Airbnb's robots.txt rules.
  • No API key is required for usage.
  • Returns structured JSON data for easy integration.

Use cases of Airbnb MCP Server?

  1. Finding suitable Airbnb accommodations for travel.
  2. Retrieving detailed information about specific listings for comparison.
  3. Integrating Airbnb search functionality into other applications.

FAQ from Airbnb MCP Server?

  • Can I use this server without an API key?

Yes! The Airbnb MCP Server does not require an API key to function.

  • Is it possible to ignore robots.txt rules?

Yes! You can configure the server to ignore robots.txt rules if needed.

  • What programming language is required to run this server?

You need Node.js installed on your machine to run the Airbnb MCP Server.

Server Config

{
  "mcpServers": {
    "airbnb": {
      "command": "npx",
      "args": [
        "-y",
        "@openbnb/mcp-server-airbnb",
        "--ignore-robots-txt"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
openbnb-org
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago