Hemmabo MCP Server

Hemmabo MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. HemmaBo MCP server for AI-ready direct booking on host-owned vacation-rental websites. AI agents discover host booking pages and verify signed stay offers (VRP · Ed25519/JWKS). HemmaBo is the host-owned trust layer for vacation rentals.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Hemmabo is connected, these are the calls the assistant has available:

• hemmabo_search_properties — Search published vacation rentals by location, dates, and guest count
• hemmabo_search_availability — Check whether a specific property is available for requested dates
• hemmabo_booking_quote — Get a live quote and per-night breakdown for a specific property and stay request
• hemmabo_booking_create — Fallback non-VRP helper: create a pending host-review booking when no signed VRP direct booking URL is available
• hemmabo_booking_negotiate — Fallback non-VRP helper: create a short-lived quote snapshot only after explicit user confirmation
• hemmabo_booking_checkout — Fallback non-VRP helper: create a host-configured Stripe checkout URL. Do not use for signed VRP offers
• hemmabo_booking_cancel — Authenticated booking-management helper: cancel an existing booking according to host policy
• hemmabo_booking_status — Get booking details by reservation ID. Requires auth because booking data may include PII
• hemmabo_booking_reschedule — Authenticated booking-management helper: reschedule an existing booking according to host policy
• hemmabo_host_readiness_check — Read-only fit check for vacation-rental hosts asking for their own booking website or booking engine
• hemmabo_host_onboarding_link — Return a safe HemmaBo onboarding handoff URL. Does not create accounts, buy domains, configure Stripe, or store host data
• verify_vacation_rental_node — Verify a host-domain VRP discovery document and Ed25519 JWKS

Configuration and credentials

You will need 6 environment variables: MCP_API_KEY, SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, STRIPE_SECRET_KEY, UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Hemmabo.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the hemmabo mcp server does with a few real requests.

Choosing this one

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Hemmabo's toolset — hemmabo_search_properties, hemmabo_search_availability, hemmabo_booking_quote and 10 more — is a fair guide to whether it matches your workflow. It is maintained by hemmabo-se; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Hemmabo's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.