tickadoo® MCP Server

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 680+ cities worldwide.

🌐 Languages: Landing page available in: EN · JA · 中文 · 한국어 · DE · FR · ES · IT · PT · tlhIngan Hol 🖖

日本語

tickadoo® MCPサーバーは、AIアシスタント（Claude、ChatGPT、Gemini等）から680以上の都市で13,000以上の体験（劇場、ツアー、アトラクション）を検索できます。APIキー不要、認証不要、即座に接続可能です。

mcp.tickadoo.com

中文

tickadoo® MCP服务器让AI助手（Claude、ChatGPT、Gemini等）可以搜索680+城市中13,000+体验活动（剧院、旅游、景点）。无需API密钥，无需认证，即时连接。

mcp.tickadoo.com

한국어

tickadoo® MCP 서버는 AI 어시스턴트(Claude, ChatGPT, Gemini 등)에서 680+ 도시의 13,000+ 체험(극장, 투어, 관광명소)을 검색할 수 있습니다.

mcp.tickadoo.com

Current release: v1.4.1

• 17 read-only MCP tools with search, comparison, city-guide, family-day, transfer, and local travel-tip workflows

• 13,090 products across 681 cities in 40+ languages

• Rule-based audience + tag enrichment (100% coverage)

• Availability slots with real dates and prices

• Booking contract with checkout deep links + Ghost Checkout

• Accessibility data for 30 London theatre venues

• Full Agent Intelligence Layer on both search tools:

  • _available_filters (10 fields: tag_counts, price_range, duration_range, audience, setting, physical, languages, tags, wheelchair, free_cancellation)

  • _conversation_starters (contextual prompts based on result data)

  • _related_searches (tag-based follow-up suggestions)

  • _booking_urgency (conversion signals: TODAY availability, free cancellation, rating, wheelchair)

  • _cross_sell, _intent_token, _accessibility

  • 📊 Result summary line + 🔍 filter hints in text responses

  • 🔥 Urgency signals in text detail responses

• Smart Filter Recovery (guides agents when filters are too restrictive)

• 1 machine-readable product feed resource

• Remote HTTP endpoint for hosted MCP clients

• Local stdio entrypoint for desktop and development workflows

Tools

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

Resource

Connect

Hosted MCP endpoint:

https://mcp.tickadoo.com/mcp

Claude / Cursor

Example remote MCP config:

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

Claude Dispatch

Claude Dispatch uses the same remote MCP URL config:

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

Gemini CLI

Add this to ~/.gemini/settings.json:

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

Perplexity

Use Perplexity's custom remote connector:

• Settings → Connectors → Custom connector → Remote

• Name: tickadoo

• MCP Server URL: https://mcp.tickadoo.com/mcp

• Transport: Streamable HTTP

• Auth: None

• Available to Perplexity paid subscribers

ChatGPT

Available to ChatGPT Pro, Business, Enterprise, and Edu plans:

1. Open Settings → Apps & Connectors → Advanced → Developer Mode ON

2. Back in Apps & Connectors → Create

3. Name: tickadoo

4. URL: https://mcp.tickadoo.com/mcp

5. Auth: None

6. In a new chat: + → More → Developer Mode → Add sources → tickadoo

Android Studio / Firebase Studio

The same httpUrl config works in:

• Android Studio (mcp.json)

• Firebase Studio (.idx/mcp.json or .gemini/settings.json)

Local Development And Stdio

Run from npm after publish:

npx -y @tickadoo/mcp-server

Example stdio config via npx:

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

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

• Glama: https://glama.ai/mcp/servers/tickadoo/tickadoo-mcp

• mcp.so: https://mcp.so/server/tickadoo-mcp

• PulseMCP: https://www.pulsemcp.com/servers/tickadoo

• tickadoo: https://www.tickadoo.com

Development Commands

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

Brand

tickadoo® is always lowercase. The tagline is What Do You Wanna Doo?® Please preserve lowercase in all integrations and documentation.

License

MIT — tickadoo Inc.