Discover and book theatre, tours, attractions, and live experiences worldwide. No API key required.
MCPpedia last refreshed this data
io.github.tickadoo/tickadoo-mcp is an MCP server that discover and book theatre, tours, attractions, and live experiences worldwide. No API key required. Its tool list has not been published yet over stdio and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"tickadoo": {
"url": "https://mcp.tickadoo.com/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Discover and book theatre, tours, attractions, and live experiences worldwide. No API key required.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @tickadoo/mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ecommerce / entertainment
The official MCP Server for the Mux API
Give Claude the ability to watch and understand videos — Claude Code plugin with frame extraction and multimodal audio analysis
Which credit card earns the most at a merchant, from your cards or every card, and why.
Dutch construction facts with measured accuracy + NL coordination. Never holds third-party funds.
MCP Security Weekly
Get CVE alerts and security updates for io.github.tickadoo/tickadoo-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
tickadoo's MCP server lets AI assistants discover and compare theatre, tours, attractions, hidden gems, and other live experiences worldwide. The full MCP surface can return live availability and tickadoo booking links. No account or API key is required.
Remote (Streamable HTTP), no install:
{ "mcpServers": { "tickadoo": { "url": "https://mcp.tickadoo.com/mcp" } } }
Or the npm bridge for stdio clients:
npx -y @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:
https://mcp.tickadoo.com/mcp
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.
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. The portable OpenAI/Codex package uses the separate
discovery-only endpoint https://mcp.tickadoo.com/mcp/agents; it does not
return direct purchase, transaction, or checkout links. OpenAI's plugin
directory reads extensions.com.openai from the root manifest.
The npm stdio bridge, MCP Registry, Claude, the copy-ready Copilot cloud MCP
adapter, Gemini, Smithery, Muse, and direct integrations retain the established
full endpoint https://mcp.tickadoo.com/mcp. The Copilot portable-plugin
marketplace entry installs the root public-agent package instead. The two
surfaces are intentionally distinct. .codex-plugin/plugin.json remains the
compatibility form of the portable public-agent package.
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, validation, release, and rollback process. The portal-only OpenAI
handoff is in
docs/openai-plugin-submission.md.
Direct OpenAI Agents API integrations that intentionally use the established
full MCP surface are documented in
docs/openai-agents-api.md. That integration is
separate from the public Plugin Directory package. Use
https://mcp.tickadoo.com/mcp — the bare host is a human-readable service
landing page, not a Streamable HTTP endpoint.
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.
Use the hosted remote directly when your MCP client supports Streamable HTTP:
{
"mcpServers": {
"tickadoo": {
"url": "https://mcp.tickadoo.com/mcp"
}
}
}
Use the npm package when your MCP client needs a local stdio command:
{
"mcpServers": {
"tickadoo": {
"command": "npx",
... [View full README on GitHub](https://github.com/tickadoo/tickadoo-mcp#readme)