compare_experiences — tickadoo mcp MCP Tool
compare_experiences
(compare experiences) is one of 23 tools on the
tickadoo mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_experiences from your client
- Claude Code tickadoo mcp compare_experiences run in your project directory
- Claude Desktop tickadoo mcp compare_experiences ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor tickadoo mcp compare_experiences ~/.cursor/mcp.json
- VS Code tickadoo mcp compare_experiences .vscode/mcp.json
- Zed tickadoo mcp compare_experiences ~/.config/zed/settings.json
- Windsurf tickadoo mcp compare_experiences ~/.codeium/windsurf/mcp_config.json
- Cline tickadoo mcp compare_experiences ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI tickadoo mcp compare_experiences ~/.gemini/settings.json
- Grok tickadoo mcp compare_experiences .mcp.json (in your project root)
- ChatGPT tickadoo mcp compare_experiences Settings → Connectors → Advanced → Developer mode
- Claude.ai tickadoo mcp compare_experiences Settings → Connectors → Add custom connector
- LangChain tickadoo mcp compare_experiences pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tickadoo-mcp https://mcp.tickadoo.com/mcpOther tools on this server
- 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
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.