Tickadoo MCP

What tickadoo/tickadoo-mcp MCP server does

tickadoo/tickadoo-mcp MCP server exposes tickadoo’s experiences catalogue through MCP. The available tools cover discovery, planning, availability checks, comparisons, and travel guidance for destinations with bookable inventory. Supported content includes theatre, musicals, concerts, comedy, tours, sightseeing, food activities, nightlife, cruises, sports, workshops, family activities, and other experiences.

Search tools can filter by city, free-text terms, category, local-currency price range, dates, and sort order. A separate mood search maps intents such as romantic, family-friendly, cultural, relaxing, luxury, or budget-oriented to relevant catalogue filters. Nearby searches accept a geographic location, while city and weekly tools help users plan activities before or during a trip.

The server returns booking links rather than requiring the MCP client to complete the transaction. Bookings are completed on tickadoo.com.

How it works

The repository’s local package is a thin stdio bridge. It forwards MCP requests to the hosted Streamable HTTP endpoint at https://mcp.tickadoo.com/mcp, including tool discovery and tool calls. The remote service owns the current tool definitions, input schemas, responses, and errors, so the live tool list can change independently of the local bridge.

A client can connect directly to the hosted endpoint when it supports Streamable HTTP. Clients that require a local process can launch the npm package with npx; the bridge then communicates with the remote service. Tool arguments such as a city, query, experience identifier, or date are sent to tickadoo to fulfill the request.

Most returned booking URLs can be localized by passing a language code. The tools document support for more than 40 languages, with examples including German, French, Spanish, and Japanese.

Setup and configuration

For a Streamable HTTP-capable MCP client, configure the remote URL directly:

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

For a local stdio connection, use the package entrypoint:

{
  "mcpServers": {
    "tickadoo": {
      "command": "npx",
      "args": ["-y", "@tickadoo/mcp-server"]
    }
  }
}

TICKADOO_MCP_URL can replace the default remote endpoint with another compatible Streamable HTTP MCP URL. TICKADOO_LOG_LEVEL=none suppresses bridge status messages on stderr. No account, API key, or personal data is required to operate the server.

Tools and capabilities

The catalogue includes general search, mood-based search, nearby discovery, city listing, city guides, weekly schedules, tonight’s events, and last-minute activities. Planning-oriented tools can create a family day, provide airport or station transfer estimates, and return local advice for 20 launch cities, including transport, safety, money, weather, connectivity, emergency numbers, and phrases.

Experience-specific tools can check one date’s availability, retrieve detailed venue and image information, and compare two to five experiences. Comparison results include differences such as price, duration, reviews, accessibility, and cancellation policy, along with callouts for value, rating, popularity, and family suitability.

Limitations and notes

tickadoo/tickadoo-mcp depends on the hosted tickadoo backend for its live catalogue and tool definitions. The local repository does not maintain a separate catalogue or local booking system. Availability, pricing, inventory signals, and booking links come from tickadoo and may vary by date, location, and experience.

The travel-tips tool contains hardcoded advice for 20 launch cities, so that coverage is narrower than the broader catalogue. Transfer information also uses known default arrival hubs for supported cities. Tool arguments are forwarded to the tickadoo backend; the bridge itself adds no tracking and does not ask for credentials.

Use tickadoo/tickadoo-mcp when an agent needs structured activity discovery or trip-planning data. It is less suitable when the client must execute the final purchase inside the MCP session, because the returned booking flow leads to tickadoo.com.