tickadoo® MCP Server

Name: tickadoo
Author: tickadoo

tickadoo® MCP Server brings live experience discovery to AI assistants through the Model Context Protocol (MCP). It gives compatible clients access to bookable theatre, shows, tours, attractions, and events across 700+ cities worldwide.

Current release: v1.1.0

4 read-only MCP tools
1 machine-readable product feed resource
Remote HTTP endpoint for hosted MCP clients
Local stdio entrypoint for desktop and development workflows

Tools

Tool	Description
`search_experiences`	Search for bookable experiences in a specific city with city fallback matching
`find_nearby_experiences`	Find experiences near a geographic location using latitude, longitude, and radius
`list_cities`	Browse supported cities with optional filtering and result limits
`get_experience_details`	Get detailed availability, pricing, venue, and image information for a specific tickadoo experience using a slug or booking path

All tools expose MCP tool annotations for readOnlyHint, destructiveHint, and openWorldHint.

Resource

Resource	Description
`tickadoo://product-feed`	Machine-readable product feed in OpenAI Commerce Product Feed format

Remote HTTP Endpoint

Hosted MCP endpoint:

https://mcp.tickadoo.com/mcp

Example remote MCP config:

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

Local Development And Stdio

Install and build:

npm install
npm run build

Run the stdio server directly:

node dist/index.js

Example stdio config:

{
  "mcpServers": {
    "tickadoo": {
      "command": "node",
      "args": ["/path/to/tickadoo-mcp/dist/index.js"]
    }
  }
}

Published Links

Landing page: https://mcp.tickadoo.com
Remote MCP endpoint: https://mcp.tickadoo.com/mcp
Smithery: https://smithery.ai/server/tickadoo/tickadoo-mcp
tickadoo: https://www.tickadoo.com

Development Commands

Command	Purpose
`npm run build`	Compile the TypeScript server
`npm run e2e:stdio`	Run the MCP smoke suite against the local stdio server
`npm run e2e:http`	Run the MCP smoke suite against an HTTP endpoint
`npm run dev:http`	Start the local HTTP development server
`npm run sync:html`	Sync `public/index.html` into the Vercel landing page handler

Architecture

Shared server logic lives in src/shared/*, including the API client, formatting, tool definitions, and resource registration. The two entrypoints are intentionally thin transport wrappers:

src/index.ts for local stdio usage
api/mcp.ts for hosted HTTP usage

This keeps stdio and HTTP behavior aligned while supporting both local and remote MCP clients.

Environment Variables

Variable	Default	Description
`TICKADOO_API_BASE`	`https://api.tickadoo.com`	tickadoo API base URL
`TICKADOO_SITE_BASE`	`https://www.tickadoo.com`	tickadoo website base URL