# HemmaBo MCP server

> Find vacation rentals on host-owned domains and verify signed stay offers before sending guests to the host's own booking page.

- Listing: https://mcp.tc/i/hemmabo
- Connect: use the server's own URL `https://www.hemmabo.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Travel & Maps](https://mcp.tc/c/travel-maps)
- Vendor: HemmaBo
- Homepage: <https://www.hemmabo.com>
- Repository: <https://github.com/HemmaBo-se/hemmabo-mcp-server>
- Package: npm `hemmabo-mcp-server`

## About

HemmaBo connects to host-owned vacation rental websites. You can search properties by region and dates, check availability, verify a host domain under the Vacation Rental Protocol (VRP), and fetch an Ed25519-signed stay offer with the host's direct booking URL. Two further tools help hosts check fit and get an onboarding link.

The server is a hosted Streamable HTTP endpoint at https://www.hemmabo.com/mcp. All six tools are read-only. No sign-in or API key is needed for the discovery tools. The server does not book or take payment; guests book and pay on the host's site.

## What it can do

- Search vacation rentals by region, country, guests and dates
- Check availability of a specific property
- Verify a host domain as a valid VRP node
- Fetch a signed stay offer with price and direct booking URL
- Check whether HemmaBo fits a host's booking website needs
- Get an onboarding link for hosts

## Tools (6)

- `hemmabo_search_properties`: Search available vacation rentals by location and dates; returns host domain and booking URL. (read-only)
- `hemmabo_check_availability`: Yes/no availability check for one property and dates, without a signed price. (read-only)
- `hemmabo_check_host_readiness`: Read-only fit check for hosts evaluating HemmaBo for their own booking site. (read-only)
- `hemmabo_get_host_onboarding_link`: Return an onboarding handoff URL for a host ready to start. (read-only)
- `vrp_verify_node`: Verify a host domain's VRP discovery document and JWKS. (read-only)
- `vrp_get_verified_stay_offer`: Fetch and verify a host-signed stay offer with final price and booking link. (read-only)

## Example prompts

- "Find a vacation rental in Skåne, Sweden for 4 guests, July 10 to 17."
- "Is this property free from 2026-12-20 to 2026-12-27?"
- "Verify the host domain villaakerlyckan.se and get a stay offer for 2 guests."
- "I'm a host with my own domain. Does HemmaBo fit my property?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http hemmabo https://www.hemmabo.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **hemmabo** and choose **Authenticate**. A browser window opens for the HemmaBo sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **HemmaBo** and paste this URL:

```url
https://www.hemmabo.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when HemmaBo asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=HemmaBo&connectorUrl=https%3A%2F%2Fwww.hemmabo.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://www.hemmabo.com/mcp` and click **Add**.

3. Click **Connect** and sign in when HemmaBo asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://www.hemmabo.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to HemmaBo to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=hemmabo&config=eyJ1cmwiOiJodHRwczovL3d3dy5oZW1tYWJvLmNvbS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "hemmabo": {
      "url": "https://www.hemmabo.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=hemmabo&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fwww.hemmabo.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"hemmabo","type":"http","url":"https://www.hemmabo.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "hemmabo": {
      "type": "http",
      "url": "https://www.hemmabo.com/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "hemmabo": {
      "serverUrl": "https://www.hemmabo.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add hemmabo --url https://www.hemmabo.com/mcp
codex mcp login hemmabo
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.hemmabo]
url = "https://www.hemmabo.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http hemmabo https://www.hemmabo.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth hemmabo` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://www.hemmabo.com/mcp`.

## Recent changes

- 2026-11-12 02:41 UTC: 1 tool changed. Source: automatic check. Changed: vrp\_get\_verified\_stay\_offer.
- 2026-11-10 05:48 UTC: New version 7.0.14 (was 7.0.13), reported by the server. Source: automatic check.
- 2026-11-08 20:53 UTC: New version 7.0.13 (was 7.0.12), reported by the server. Source: automatic check.
- 2026-10-30 20:48 UTC: New version 7.0.12 (was 7.0.10), reported by the server. Source: automatic check.
- 2026-10-28 05:41 UTC: New version 7.0.9 (was 7.0.8), reported by the server. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/hemmabo#history (Atom feed: https://mcp.tc/i/hemmabo/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 7.0.14
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-12 (reachable)
- Listed: 2026-10-18
- Updated: 2026-10-30

---
Source: https://mcp.tc/i/hemmabo (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report