Airbnb MCP Server (Enhanced)

Created By
devyhana year ago
Enhanced MCP server for Airbnb search and listing details
Overview

What is Enhanced Airbnb MCP Server?

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

How to use Enhanced Airbnb MCP Server?

To use the server, you can either install it on your local machine or use it via Smithery. You can perform searches for listings or get detailed information about specific listings using the provided commands.

Key features of Enhanced Airbnb MCP Server?

  • Improved error handling with detailed messages
  • Enhanced logging for easier debugging
  • Type safety with better TypeScript definitions
  • Modularized code structure for maintainability
  • Optimized performance for network requests
  • Richer results with detailed listing information
  • Compliance with Airbnb's robots.txt rules

Use cases of Enhanced Airbnb MCP Server?

  1. Searching for Airbnb listings in various locations.
  2. Retrieving detailed information about specific Airbnb properties.
  3. Integrating Airbnb data into applications for travel planning.

FAQ from Enhanced Airbnb MCP Server?

  • Can I search for listings in any location?

Yes! You can search for listings by providing the location as input.

  • Is there a way to ignore robots.txt rules?

Yes, you can use an option to ignore robots.txt for all requests.

  • What programming language is the server built with?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
devyhan
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago