HemmaBo

Name: HemmaBo
Author: HemmaBo-se

@HemmaBo-se

HemmaBo について

Reference implementation: HemmaBo — the host-owned trust layer for vacation rentals: every host runs 0%-commission direct bookings on their own domain, with host-signed, agent-verifiable offers that AI agents can discover, verify, and book directly. https://hemmabo.com

#mcp #model-context-protocol #vacation-rental #direct-booking #booking #travel #lodging #vrp #verified-stay-offer #host-domain-signature #ed25519 #jwks #stripe #agentic-commerce #agentic-commerce-protocol #stripe-acp #ap2 #agent-payments-protocol

基本情報

カテゴリ

その他

ライセンス

Apache-2.0

ランタイム

node

トランスポート

stdio

公開者

HemmaBo-se

投稿者

HemmaBo

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "hemmabo": {
      "type": "http",
      "url": "https://www.hemmabo.com/mcp"
    }
  }
}

ツール

Search vacation rental properties by location and travel dates. Returns only properties that are available for the requested period and can accommodate the guest count. Each result includes live pricing with both public rates (what OTA/website visitors see) and federation rates (direct booking discount). Use region or country to filter by location. Guests parameter determines which price tier applies. Results are sorted by relevance.

Check whether a specific property is available for the requested date range. Verifies against three sources: host-blocked dates, confirmed bookings, and active booking locks (temporary holds during checkout). Returns available=true/false with conflict details if unavailable. Call this before create_booking to confirm availability, or use it to check multiple date ranges for the same property.

Get a detailed pricing quote for a specific property, date range, and guest count. Returns three price points: (1) publicTotal — the rate shown on public websites, (2) federationTotal — the direct booking rate with the host's configured discount applied, (3) gapTotal — an additional discount if the dates fill a gap between existing bookings. Also returns per-night breakdown, season classification, weekend detection, and any package pricing (7-night week or 14-night two-week discounts). All prices are integers in the property's local currency. The host controls all discount percentages.

Create a new direct booking for a property. This is a write operation that: (1) validates the property is still available for the requested dates, (2) calculates the final federation price (with gap discount if applicable), (3) creates a pending booking record that requires host approval. Returns the booking ID, final price, and confirmation details. The booking status starts as 'pending' until the host approves. Guest contact details are required for the host to follow up.

Create a binding price quote with a quoteId. Calculates federation pricing (with gap/package discounts) and stores an immutable snapshot in property_quote_snapshots. The quoteId can be passed to checkout to lock the price. Quote expires after 15 minutes. Returns publicTotal, federationTotal, per-night breakdown, package info, and the quoteId.

Create a booking with Stripe payment. Creates a Stripe Checkout Session and a booking record. If a quoteId from negotiate_offer is provided, the price is locked to that quote. Supports MPP (Machine Payments Protocol): set paymentMode to 'payment_intent' to receive a client_secret for programmatic payment instead of a redirect URL. Returns reservationId, paymentUrl, and MPP block with payment details.

Cancel a booking. Delegates to the Supabase Edge Function cancel-booking which handles refund calculation based on the host's cancellation policy, Stripe refund processing, email notifications, and blocked date cleanup. Returns the cancellation status and refund details (amount, percentage, reason, Stripe refund ID).

Get the current status and details of a booking. Returns booking information (dates, guests, price, status), property details (name, domain), and the applicable cancellation policy (tier and refund rules). Use this to check on a booking after creation or before attempting a reschedule or cancellation.

Reschedule a booking to new dates. Validates that the booking is in a reschedulable state (confirmed or pending), checks availability for the new dates (excluding the current booking from conflict detection), recalculates the price, and handles the Stripe charge/refund for any price delta. If the new price is higher, a new PaymentIntent with manual capture is created. If lower, a partial refund is issued on the original PaymentIntent. Returns previous and new dates, pricing details, and any Stripe action taken.

概要

What is HemmaBo?

HemmaBo is an MCP server that enables AI-ready direct booking on host-owned vacation-rental domains. It lets AI agents discover host booking pages, verify signed stay offers (VRP · Ed25519/JWKS), and read live availability, pricing, and direct booking links. It is not an OTA or marketplace.

How to use HemmaBo?

Connect an MCP client to the hosted Streamable HTTP endpoint at https://www.hemmabo.com/mcp. No local install is needed. Anonymous calls are read-only; mutating booking tools require a Bearer token or OAuth credentials. For VRP offers, route the guest to the signed direct host-domain booking URL returned by the verified offer.

Key features of HemmaBo

Verifies host-domain signed VRP stay offers (Ed25519/JWKS)
Searches published HemmaBo vacation-rental properties
Checks live availability and provides per-night pricing quotes
Offers fallback booking helpers for non-VRP deployments
Supports AP2 Cart Mandate verification for agent payments
Public-read, signed-write authentication model

Use cases of HemmaBo

Helping a vacation-rental host evaluate HemmaBo for an own-domain booking website
Searching published HemmaBo properties by location, dates, and guest count
Verifying a signed host-domain offer before quoting it to a guest
Getting a live quote and per-night breakdown for a specific property and stay
Checking availability for requested dates across one or more properties

FAQ from HemmaBo

What data does HemmaBo require?

HemmaBo requires a Supabase URL and service role key. Optionally, a Stripe secret key enables fallback checkout helpers, and an MCP API key enables Bearer-token auth for protected tools.

How does HemmaBo handle authentication?

Anonymous calls are public and read-only. Mutating booking tools and booking-status reads require an Authorization: Bearer <token> header, using the configured MCP_API_KEY or OAuth client credentials.

Where does booking data live?

Bookings are managed on host-owned domains via VRP signed offers. HemmaBo does not become the merchant of record or store guest payment data. For fallback non-VRP deployments, booking lifecycle helpers operate with the host's own Stripe account.

What transports does HemmaBo support?

Streamable HTTP at the hosted /mcp endpoint. HemmaBo is remote-only with no local/stdio install.

Does HemmaBo support OTA-like booking?

No. HemmaBo is not an OTA, marketplace, or hotel search engine. For VRP offers the booking path is always the signed direct host-domain URL. Fallback helpers exist only for configured non-VRP deployments.