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.
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.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@tickadoo/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @tickadoo/mcp-server against OSV.dev.
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
AI Skills, MCP Tools, and CLI for Unity Engine. Full AI develop and test loop. Use cli for quick setup. Efficient token usage, advanced tools. Any C# method may be turned into a tool by a single line. Works with Claude Code, Gemini, Copilot, Cursor and any other absolutely for free.
Music studio: ABC notation composition and Strudel live coding with ext-apps UI.
YouTube as a queryable database for AI agents. 41 tools, zero config.
The official MCP Server for the Mux API
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/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
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",
"args": ["-y", "@tickadoo/mcp-server"]
}
}
}
Set TICKADOO_MCP_URL to point the bridge at another compatible Streamable HTTP MCP endpoint:
TICKADOO_MCP_URL=http://127.0.0.1:8787/mcp npx -y @tickadoo/mcp-server
Set TICKADOO_LOG_LEVEL=none to silence bridge status logs on stderr.
npm install
npm run build
npm test
Run the built stdio bridge:
node dist/index.js
Refresh the MCP registry metadata from the live remote:
npm run sync:server-json
Run the optional live integration test:
LIVE=1 npm test
The current tool list is served by the remote MCP server. Visit mcp.tickadoo.com or run npm run sync:server-json to refresh the registry metadata in this repo.