Stayingapi mcp

Skill stayingapi/travel-skills/skills/stayingapi-mcp

Portable AI-agent skills (SKILL.md) for accommodation search, availability, pricing, cross-OTA comparison & reviews via StayingAPI. Works with Claude, MCP and more. MIT-0.

Install

npx -y skills add stayingapi/travel-skills --skill stayingapi-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Connect an AI agent to the StayingAPI Model Context Protocol (MCP) server for accommodation search, availability, pricing, cross-OTA price comparison and reviews. Use when the agent runtime supports MCP connectors (e.g. Claude) and you want OAuth-based access without managing API keys. Covers the OAuth 2.1 + PKCE connect flow, the seven read-only tools, and when to prefer MCP vs REST.

The file declares its own license as Proprietary — see https://stayingapi.com/terms. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.1 KB, as published. Nobody here has run it

StayingAPI — connect the MCP server

StayingAPI ships a native Model Context Protocol server so an agent can query accommodation data across Airbnb, Booking.com, Vrbo and Google Hotels as first-class tools — no API key pasted into the agent.

Server URL: https://mcp.stayingapi.com/mcp (Streamable HTTP transport).
Auth: OAuth 2.1 + PKCE (S256) with dynamic client registration. You authorize once in a browser popup; the connector is linked to your StayingAPI account and its credit balance.
OAuth protected-resource metadata (RFC 9728): https://mcp.stayingapi.com/.well-known/oauth-protected-resource

Connect (Claude.ai / Claude Desktop / Claude Code)

Open your agent's connector settings and add a custom connector (MCP server).
Use the URL https://mcp.stayingapi.com/mcp.
Complete the OAuth prompt in the browser popup — this links the connector to your StayingAPI account. (First-time users: create an account and verify email first; a sandbox account works for evaluation. See https://stayingapi.com/docs/mcp.)
The seven tools below become available to the agent.

The seven read-only tools

search_stays — search stays across platforms by location, dates, occupancy, filters.
check_availability — day-by-day availability for a known listing over a date window.
get_listing — full detail for one listing (amenities, photos, host, ratings).
get_price — a real price quote for one listing for specific dates + occupancy.
compare_prices — compare one property across OTAs with computed min + median.
get_reviews — normalized, paginated reviews for one listing on one platform.
get_job — poll status + fetch results of an async scrape job (costs 0).

Async behavior

The tools share the same async contract as REST: a live call that has to scrape returns a pending job; the agent (or the tool layer) polls get_job with the returned jobId until it completes, and the result payload arrives under data.result. Sandbox and cache hits return immediately.

Credits & limits

MCP calls draw from the same single credit balance as your REST keys, but are rate-limited on a separate per-user bucket. Costs and rate limits: https://stayingapi.com/pricing.

MCP vs REST — which to use

MCP — best for interactive agents/assistants (e.g. Claude) that support connectors: OAuth instead of key management, tools surfaced natively to the model.
REST (skill: stayingapi-search) — best for programmatic backends, servers, cron jobs, and any runtime without MCP support: a Bearer key + the @stayingapi/sdk.

Both hit the same data and the same unified schema. Docs: https://stayingapi.com/docs/mcp.