Tickadoo MCP MCP server

An official Model Context Protocol server by Tickadoo that enables AI agents to search, compare, and retrieve booking links for over 12,000 bookable experiences across more than 1,100 cities. It provides 23 public tools for integrating travel and attraction bookings into applications, with specific integrations for hotel platforms like Mews and Apaleo.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Tickadoo

MCP endpoint (Streamable HTTP)

https://mcp.tickadoo.com/mcp

Vendor documentation

What you can do with it

Search for bookable experiences and attractions
Compare options across 1,100+ cities
Retrieve direct booking links for users
Integrate travel bookings via Mews or Apaleo

Tools advertised by the last live check:

search_experiences
search_local_experiences
find_nearby_experiences
whats_on_tonight
get_last_minute
get_whats_on_this_week
recommend_experiences
get_city_guide
get_travel_tips
compare_experiences
get_hidden_gems
get_family_day
get_date_night
plan_itinerary
list_cities
get_experience_details
get_related_experiences
get_availability
check_availability
search_by_mood
get_transfer_info
render_experience_cards
report_quality_signal

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http tickadoo-mcp https://mcp.tickadoo.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add tickadoo-mcp --url https://mcp.tickadoo.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tickadoo-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "tickadoo-mcp": {
      "url": "https://mcp.tickadoo.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "tickadoo-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.tickadoo.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tickadoo-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "tickadoo-mcp": {
      "type": "http",
      "url": "https://mcp.tickadoo.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http tickadoo-mcp https://mcp.tickadoo.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "tickadoo-mcp": {
      "url": "https://mcp.tickadoo.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tickadoo-mcp": {
      "serverUrl": "https://mcp.tickadoo.com/mcp"
    }
  }
}

See all 353

Do you run Tickadoo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing