Skip to main content
Glama
Sign In
getyourguide-mcp

getyourguide-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

How to connect GetYourGuide to Claude Code, ChatGPT and any AI agent

Yes, Claude, ChatGPT and other AI agents can work in your GetYourGuide account. GetYourGuide's official apps in ChatGPT and Claude help travelers find and book tours, not manage a supplier account. Cotlet.dev connects your own signed-in GetYourGuide supplier account to any AI agent, so the AI lists bookings and updates availability for you.

What you can ask

List all bookings for my Lisbon sunset sailing tour this Saturday with guest names and group size.

Block availability for the 9 am Old Town walking tour from December 24 to 26.

Add a 4 pm slot to the Colosseum skip-the-line tour every Friday in December, 12 spots each.

How many bookings did each of my tours get last week? Show cancellations separately.

Cut Sunday's kayak tour to 8 spots, we only have one guide that day.

Related MCP server: realtycalendar-mcp

Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.

Claude Code

claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT

Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.

Cursor

Copy .cursor/mcp.json from this repo into your project:

{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}

Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its GetYourGuide tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

{"mcpServers":{"getyourguide":{"command":"uvx","args":["getyourguide-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}

Or with Docker:

docker build -t getyourguide-mcp .
docker run -i --rm -e COTLET_API_KEY getyourguide-mcp

Tools: getyourguide_guide, getyourguide_status, getyourguide_open, getyourguide_read, getyourguide_click, getyourguide_type, getyourguide_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Command line

Python 3.10+, nothing else to install. From PyPI:

pip install getyourguide-mcp        # or run it once: uvx getyourguide-mcp connect
getyourguide-mcp connect

Or straight from this repo:

export COTLET_API_KEY="your-key"
python3 getyourguide_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 getyourguide_agent.py status    # is GetYourGuide ready in your Cotlet.dev account
python3 getyourguide_agent.py guide     # GetYourGuide screens and sign-in link
python3 getyourguide_agent.py read      # open GetYourGuide, read the page, close the browser
python3 getyourguide_agent.py tools     # list Cotlet.dev tools
python3 getyourguide_agent.py serve     # start the stdio MCP server (same as no argument)

Questions from GetYourGuide users

Does GetYourGuide have an API?

GetYourGuide has a Supplier API, but it is built for reservation systems and channel managers that pass its connectivity testing, not for a tour operator who wants a key (checked 11 Oct 2026). Every system must implement the mandatory endpoints, and the docs describe no API for customer messages or reviews. Cotlet.dev works in your own signed-in GetYourGuide account, so your AI agent can list bookings and update availability with no API key and no code.

How do I connect GetYourGuide to ChatGPT?

Add Cotlet.dev as an app in ChatGPT (Settings → Apps, connector URL https://cotlet.dev/mcp/v1), sign in to GetYourGuide once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words. No code and no GetYourGuide API key.

Is there a way to use Claude with GetYourGuide?

Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own GetYourGuide account.

Is there a GetYourGuide MCP server?

GetYourGuide has an official Claude connector for travelers booking tours and activities. For your own supplier account, Cotlet.dev is a hosted MCP server that works in GetYourGuide for you, 24/7, with Claude, ChatGPT, Cursor, Codex, n8n, Make and Zapier.

Find it on

Also works with

More: https://cotlet.dev/integrations/getyourguide-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=getyourguide

Start free: https://cotlet.dev/signup?app=getyourguide&utm_source=github&utm_medium=readme&utm_campaign=getyourguide

Available Tools

7 tools
getyourguide_clickCInspect

Click a numbered element on the current GetYourGuide page.

Inputs: element (required).

getyourguide_closeAInspect

Close the GetYourGuide browser session when the work is done, so credits stop running.

Inputs: no named parameters.

getyourguide_guideAInspect

How to work in GetYourGuide (list bookings and update availability): its screens and the sign-in link. Call this first.

Inputs: task.

getyourguide_openAInspect

Open a GetYourGuide page in your signed-in Cloud Browser (default https://supplier.getyourguide.com) to work with list bookings and update availability.

Inputs: url.

getyourguide_readBInspect

Read the current GetYourGuide page: its text and numbered buttons, links and fields.

Inputs: element.

getyourguide_statusAInspect

Check that your Cotlet.dev account and GetYourGuide are ready: account, credits and GetYourGuide connection.

Inputs: no named parameters.

getyourguide_typeBInspect

Type text into a numbered field on the current GetYourGuide page.

Inputs: text (required), element (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guidance, readiness check, session opening, page reading, element clicking, text entry, and session closing. The browser-automation actions are cleanly separated, and there is little risk of selecting the wrong tool for a given operation.

    Naming Consistency4/5

    All tools share the same getyourguide_ prefix and use short lowercase labels, which makes the set predictable. The only minor inconsistency is that most labels are verbs while guide and status are nouns, but the pattern remains easy to understand.

    Tool Count5/5

    Seven tools is well-scoped for a browser-automation server focused on GetYourGuide workflows. Each tool supports a necessary part of the session lifecycle without adding redundant operations.

    Completeness4/5

    The core lifecycle is covered: guidance, status check, opening a page, reading elements, clicking, typing, and closing the session. Minor gaps such as explicit navigation, scrolling, waiting, or select-style interactions exist, but most GetYourGuide booking and availability tasks should be workable through click and type.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers