getyourguide-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Used to authenticate to the hosted Cotlet.dev MCP server (as a Bearer token in the Authorization header) or passed to the local stdio server via the environment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
GetYourGuide through Cotlet.dev. Call getyourguide_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getyourguide_guideA | How to work in GetYourGuide (list bookings and update availability): its screens and the sign-in link. Call this first. |
| getyourguide_statusA | Check that your Cotlet.dev account and GetYourGuide are ready: account, credits and GetYourGuide connection. |
| getyourguide_openA | Open a GetYourGuide page in your signed-in Cloud Browser (default https://supplier.getyourguide.com) to work with list bookings and update availability. |
| getyourguide_readB | Read the current GetYourGuide page: its text and numbered buttons, links and fields. |
| getyourguide_clickC | Click a numbered element on the current GetYourGuide page. |
| getyourguide_typeB | Type text into a numbered field on the current GetYourGuide page. |
| getyourguide_closeA | Close the GetYourGuide browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.