Official description7 sourcesMCP servers8d ago
tickadoo/tickadoo-mcp
Discover and book theatre, shows, events, tours
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add tickadoo-mcp -- npx -y tickadoo-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 2 ★ · tickadoo/tickadoo-mcp · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 2 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
tickadoo/tickadoo-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
tickadoo MCP: bookable experiences for AI assistants
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
tickadoo's MCP server lets any AI assistant discover, compare, and book real
experiences (theatre, tours, attractions, hidden gems) across 1,100+ cities
worldwide, with live availability and booking links. No account, no API key.
Try it
- "What's on in London tonight?"
- "Plan a 3-day food itinerary in Paris."
- "Compare walking tours in Rome."
Connect
Remote (Streamable HTTP), no install:
Or the npm bridge for stdio clients:
---
tickadoo MCP Server
@tickadoo/mcp-server is the local stdio entrypoint for tickadoo MCP. Since v2.0.0 it is a thin bridge to the canonical remote server at:
Meta Muse connector
Directory submission pack and the brief Muse should fetch live in connectors/muse/. Stable brief:
https://raw.githubusercontent.com/tickadoo/tickadoo-mcp/main/connectors/muse/muse.md
Submit at muse.ai/platform using connectors/muse/SUBMISSION.md. No API key. Discovery is this MCP server; checkout stays on tickadoo.com.
Agent Plugins 1.0
This repository is also a portable Agent Plugins 1.0.0 package. Compatible
clients discover the root plugin.json, the seven workflows in
skills/, and the credential-free Streamable HTTP configuration in
mcp.json. Current Codex marketplace ingestion uses the parallel
.codex-plugin/plugin.json adapter; the portable root manifest remains the
vendor-neutral source of truth.
Run npm run test:plugin to validate the package against the vendored official
schemas and its containment, discovery, transport, and secret-safety checks.
The same command verifies the exact npm tarball contents and the provider-neutral
acceptance corpus in evals/agent-plugin-scenarios.json.
See docs/agent-plugins.md for the architecture
decision, compatibility evidence, update/rollback process, and follow-ups.
OpenAI Agents API sessions that call the public MCP (Book path) are documented in
docs/openai-agents-api.md. Use
https://mcp.tickadoo.com/mcp — the bare host 404s.
The package no longer defines tools, formats catalogue data, or calls a local tickadoo backend. It connects to the remote Streamable HTTP MCP server and proxies tools/list, tools/call, resources/list, resources/read, and ping. The live remote owns the tool list, schemas, results, and errors.
No API key is required.
Install
Use the hosted remote directly when your MCP client supports Streamable HTTP:
Use the npm package when your MCP client needs a local stdio command:
Use Gemini CLI:
Use Claude Code's supported marketplace flow:
Configuration
Set TICKADOO_MCP_URL to point the bridge at another compatible Streamable HTTP MCP endpoint:
> Only point TICKADOO_MCP_URL at endpoints you trust: the bridge forwards your tool arguments (city names, queries, experience IDs) to whichever endpoint is configured.
Set TICKADOO_LOG_LEVEL=none to silence bridge status logs on stderr.
Local Development
Use Node.js 22+ and install Python 3 with a python3 executable on PATH
before running the checks. The registry read-back tests execute the workflow's
experiences (theatre, tours, attractions, hidden gems) across 1,100+ cities
worldwide, with live availability and booking links. No account, no API key.
Try it
- "What's on in London tonight?"
- "Plan a 3-day food itinerary in Paris."
- "Compare walking tours in Rome."
Connect
Remote (Streamable HTTP), no install:
Or the npm bridge for stdio clients:
---
tickadoo MCP Server
@tickadoo/mcp-server is the local stdio entrypoint for tickadoo MCP. Since v2.0.0 it is a thin bridge to the canonical remote server at:
Meta Muse connector
Directory submission pack and the brief Muse should fetch live in connectors/muse/. Stable brief:
https://raw.githubusercontent.com/tickadoo/tickadoo-mcp/main/connectors/muse/muse.md
Submit at muse.ai/platform using connectors/muse/SUBMISSION.md. No API key. Discovery is this MCP server; checkout stays on tickadoo.com.
Agent Plugins 1.0
This repository is also a portable Agent Plugins 1.0.0 package. Compatible
clients discover the root plugin.json, the seven workflows in
skills/, and the credential-free Streamable HTTP configuration in
mcp.json. Current Codex marketplace ingestion uses the parallel
.codex-plugin/plugin.json adapter; the portable root manifest remains the
vendor-neutral source of truth.
Run npm run test:plugin to validate the package against the vendored official
schemas and its containment, discovery, transport, and secret-safety checks.
The same command verifies the exact npm tarball contents and the provider-neutral
acceptance corpus in evals/agent-plugin-scenarios.json.
See docs/agent-plugins.md for the architecture
decision, compatibility evidence, update/rollback process, and follow-ups.
OpenAI Agents API sessions that call the public MCP (Book path) are documented in
docs/openai-agents-api.md. Use
https://mcp.tickadoo.com/mcp — the bare host 404s.
The package no longer defines tools, formats catalogue data, or calls a local tickadoo backend. It connects to the remote Streamable HTTP MCP server and proxies tools/list, tools/call, resources/list, resources/read, and ping. The live remote owns the tool list, schemas, results, and errors.
No API key is required.
Install
Use the hosted remote directly when your MCP client supports Streamable HTTP:
Use the npm package when your MCP client needs a local stdio command:
Use Gemini CLI:
Use Claude Code's supported marketplace flow:
Configuration
Set TICKADOO_MCP_URL to point the bridge at another compatible Streamable HTTP MCP endpoint:
> Only point TICKADOO_MCP_URL at endpoints you trust: the bridge forwards your tool arguments (city names, queries, experience IDs) to whichever endpoint is configured.
Set TICKADOO_LOG_LEVEL=none to silence bridge status logs on stderr.
Local Development
Use Node.js 22+ and install Python 3 with a python3 executable on PATH
before running the checks. The registry read-back tests execute the workflow's
- Source
- awesome · https://github.com/tickadoo/tickadoo-mcp
- Browse by field
- MCP servers
- Traction
- 2 ★
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.