search_toursLABSCO SUMMARY
Bookable experiences an itinerary agent can search
TicketLens gives a travel assistant one search surface over tours, museum and attraction tickets, sightseeing buses and event admissions, with a place-resolution step so "Eiffel Tower" becomes a real record before the search runs. It is a hosted connector, so there is nothing to deploy.
What it is
TicketLens Experiences is the official hosted remote MCP server for destination experiences, served at mcp.ticketlens.com. The same inventory is also available as a versioned REST API for clients that are not on MCP.
What you get
search_tours— search across providers for attraction tickets, tours and experiences, with structured availability and pricing.search_pois— resolve an attraction name or alias to a canonical place before searching it.get_tour— fetch the detail behind an experience returned by a search.health_check— confirm service status.- Coverage spans guided tours, attraction and museum tickets, hop-on hop-off buses, sports tickets and event admissions in one result set.
- Date filtering with ISO dates, for a single day or a range.
Requirements
An MCP client that can add a remote HTTP connector, pointed at the public hosted URL. The current public setup needs no extra headers, and TicketLens describes the surface as free to use.
Setup effort
One command — codex mcp add ticketlens-experiences --url https://mcp.ticketlens.com/
USE CASES
01
Resolve a landmark to a real record
Turn a user's phrasing of an attraction into the canonical place before searching it.
02
Find tickets for a named attraction on given dates
Resolve the attraction, then search its inventory filtered to the travel dates.
03
Fill an open day in an itinerary
Search a city for tours, admissions and sightseeing options in one pass.
04
Show the detail behind a suggestion
Pull the full record for one experience before recommending it.
05
Confirm the connector is live
Check service status before a booking flow depends on it.
5 tools
Listed in project docs. Your client may show a different list.
search_poisget_tourhealth_checksubmit_feedbackBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
Setup
Codex
Codex:
TERMINAL
codex mcp add ticketlens-experiences --url https://mcp.ticketlens.com/Cursor: add the hosted MCP URL https://mcp.ticketlens.com/ to your Cursor MCP config (see the Cursor tab)
Claude: remote MCP connectors are added from the UI — use https://mcp.ticketlens.com/ in Settings > Connectors
Non-MCP clients: call the public REST API at https://api.ticketlens.com/v1 directly
Hosted endpoint
ENDPOINT URL
https://mcp.ticketlens.com/Add this hosted endpoint to your MCP client.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"ticketlens-experiences": {
"url": "https://mcp.ticketlens.com/"
}
}
}Claude Desktop
Claude remote MCP connectors are added from the UI, not through claude_desktop_config.json. Use the hosted URL https://mcp.ticketlens.com/ in Settings > Connectors
OpenClaw
Add a workspace skill that calls the public TicketLens REST API — start from examples/openclaw/skills/ticketlens-api/SKILL.md
