MCP server

If you work in Claude, ChatGPT or another MCP client rather than writing code, this is the Dyme Affiliates API as a set of tools. Ask for hotels in a place or one hotel by name, and you get back each hotel's name, star rating, guest score, photos, and a link to Dyme with your code on it. It doesn't book anything.

This server is for affiliates. A traveller who wants live prices and to book for themselves should connect to Dyme at https://mcp.dyme.earth/api/mcp instead.

The tools are generated from the OpenAPI document, one per endpoint, with the same parameters as arguments.

Endpoint

https://affiliates.dyme.earth/mcp

Transport: Streamable HTTP. No SSE, no login. This address won't change.

Configuration

Without a key:

{ "mcpServers": { "dyme": { "url": "https://affiliates.dyme.earth/mcp" } } }

With an affiliate key:

{
  "mcpServers": {
    "dyme": {
      "url": "https://affiliates.dyme.earth/mcp",
      "headers": { "Authorization": "Bearer dyme_live_YOUR_KEY" }
    }
  }
}

Authentication

Optional, and the same key as the API. Without one you get the keyless limit (30 requests an hour per IP address) and links with no affiliate code. With one, links carry your code and your key's allowance applies, shared with the API.

Tools

Tool	Endpoint
search_hotels	GET /hotels/search
find_hotel	GET /hotels/find
get_hotel	GET /hotels/{id}
make_links	POST /links

Arguments, responses and errors are the endpoint's; see the API reference. A refused call comes back with isError: true and the endpoint's error code in structuredContent.error. A rate limit tells you when to retry.

Booking

The server hands back a link to the hotel's page and stops there. The traveller sees prices on Dyme, signs in at checkout and pays there. No payment details pass through the client.

Display rules

The display rules apply to anything the server returns.