Ticketlens Experiences MCP Server

Most developer tooling work still happens through a UI a human drives. Ticketlens Experiences MCP MCP server moves it into the conversation instead. Official remote MCP server and REST API for discovering tours, tickets, attractions, and activities with TicketLens.

The short version

• Hosted remote MCP server with a public URL for quick connector setup and evaluation
• Public REST fallback on the same inventory for clients that are not using MCP yet
• Broad destination-experiences coverage across tours, attraction tickets, hop-on hop-off buses, sports tickets, and events

The tools it exposes

The server publishes 11 tools. What each one is for:

• hop — on hop-off bus products
• search_tours — search_pois
• get_tour — health_check
• ReDoc — https://api.ticketlens.com/v1/redoc
• Method — Path
• POST — /v1/search/tours
• GET — /v1/tours/{tour_id}
• Codex — If you manage Codex MCP servers through config files, start from examples/mcp/codex-config.toml
• Cursor — Add the hosted MCP URL to your Cursor MCP config. A ready-to-copy example is in examples/mcp/cursor-mcp.json
• Claude — Claude remote MCP connectors are added from the UI, not through claude_desktop_config.json. Use the hosted URL https://mcp.ticketlens.com/ in
• OpenClaw — OpenClaw users can integrate TicketLens quickly by adding a workspace skill that calls the public TicketLens REST API. Start from

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ticketlens Experiences MCP's toolset — hop, search_tours, get_tour and 8 more — is a fair guide to whether it matches your workflow. It is maintained by ticketlens; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ticketlens Experiences MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.