HemmaBo
@HemmaBo-se
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
Overview
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.
