{
  "markdown": "# tickadoo MCP Server\n\n`@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:\n\n```text\nhttps://mcp.tickadoo.com/mcp\n```\n\n## Agent Plugins 1.0\n\nThis repository is also a portable Agent Plugins 1.0.0 package. Compatible\nclients discover the root [`plugin.json`](plugin.json), the seven workflows in\n[`skills/`](skills/), and the credential-free Streamable HTTP configuration in\n[`mcp.json`](mcp.json). Current Codex marketplace ingestion uses the parallel\n`.codex-plugin/plugin.json` adapter; the portable root manifest remains the\nvendor-neutral source of truth.\n\nRun `npm run test:plugin` to validate the package against the vendored official\nschemas and its containment, discovery, transport, and secret-safety checks.\nThe same command verifies the exact npm tarball contents and the provider-neutral\nacceptance corpus in [`evals/agent-plugin-scenarios.json`](evals/agent-plugin-scenarios.json).\nSee [`docs/agent-plugins.md`](docs/agent-plugins.md) for the architecture\ndecision, compatibility evidence, update/rollback process, and follow-ups.\n\nThe 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.\n\nNo API key is required.\n\n## Install\n\nUse the hosted remote directly when your MCP client supports Streamable HTTP:\n\n```json\n{\n  \"mcpServers\": {\n    \"tickadoo\": {\n      \"url\": \"https://mcp.tickadoo.com/mcp\"\n    }\n  }\n}\n```\n\nUse the npm package when your MCP client needs a local stdio command:\n\n```json\n{\n  \"mcpServers\": {\n    \"tickadoo\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@tickadoo/mcp-server\"]\n    }\n  }\n}\n```\n\nUse Gemini CLI:\n\n```bash\ngemini extensions install https://github.com/tickadoo/tickadoo-mcp\n```\n\n## Configuration\n\nSet `TICKADOO_MCP_URL` to point the bridge at another compatible Streamable HTTP MCP endpoint:\n\n```bash\nTICKADOO_MCP_URL=http://127.0.0.1:8787/mcp npx -y @tickadoo/mcp-server\n```\n\nSet `TICKADOO_LOG_LEVEL=none` to silence bridge status logs on stderr.\n\n## Local Development\n\n```bash\nnpm install\nnpm run build\nnpm test\n```\n\nRun the built stdio bridge:\n\n```bash\nnode dist/index.js\n```\n\nRefresh the MCP registry metadata from the live remote:\n\n```bash\nnpm run sync:server-json\n```\n\nRun the optional live integration test:\n\n```bash\nLIVE=1 npm test\n```\n\n## Live Tools\n\nThe current tool list is served by the remote MCP server. Visit [mcp.tickadoo.com](https://mcp.tickadoo.com) or run `npm run sync:server-json` to refresh the registry metadata in this repo.\n\n## Privacy & Data Handling\n\n- **No account or API key required.** The server is read-mostly: it exposes tickadoo's public experiences catalogue (search, recommendations, availability, comparison, itineraries) and returns booking links — it does not collect, store, or require personal data to function.\n- **What is sent:** tool arguments (e.g. a city name, query text, or chosen experience id) are forwarded to the tickadoo backend to fulfil the request. The bridge adds no tracking and asks for no credentials.\n- **First-party service.** tickadoo is the operator of the catalogue and backend; supplier inventory is presented as tickadoo. Bookings are completed on tickadoo.com.\n- **Full policy:** [tickadoo.com/privacy](https://tickadoo.com/privacy). Questions: support@tickadoo.com.\n",
  "bytes": 3515,
  "sha": "5a850537d23bcf2c633b1252c611d6084bb0b9f71d17c7488a0fc1a82b71c115",
  "repo_slug": "tickadoo/tickadoo-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_tickadoo_tickadoo_mcp_67dbb50c/readme"
}