TicketLens Experiences MCP

Official remote MCP server and REST API for discovering tours, tickets, attractions, and activities with TicketLens.

TicketLens provides a public hosted remote MCP server athttps://mcp.ticketlens.com/and a versioned REST API athttps://api.ticketlens.com/v1for AI travel planners, destination discovery flows, and custom integrations. The same hosted inventory covers guided tours, attraction tickets, hop-on hop-off buses, sports tickets, and other event tickets.

- The official TicketLens remote MCP + REST surface for destination experiences.
- A developer-facing search surface for destination experiences.
- Available as both MCP and REST on the same hosted inventory.
- Designed for AI assistants, travel planning tools, destination discovery flows, and custom integrations.

- 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 publictour-named tools and endpoints return a broader destination-experiences catalog, not just guided tours.

search_toursandPOST /v1/search/tourscan return:

- guided tours
- attraction and museum tickets
- hop-on hop-off bus products
- sports tickets
- event and admission products

- search_tours
- search_pois
- get_tour
- health_check
- submit_feedback

- POST /v1/search/tours
- GET /v1/tours/{tour_id}
- POST /v1/search/pois
- GET /v1/pois/{poi_id}
- GET /v1/livez
- GET /v1/readyz
- GET /v1/health
- GET /v1/openapi.json
- GET /v1/docs
- GET /v1/redoc

- Base URL:https://mcp.ticketlens.com/
- Canonical server card:https://mcp.ticketlens.com/.well-known/mcp/server-card.json
- Compatibility alias:https://mcp.ticketlens.com/.well-known/mcp.json

codex mcp add ticketlens-experiences --url https://mcp.ticketlens.com/

If you manage Codex MCP servers through config files, start fromexamples/mcp/codex-config.toml.

Add the hosted MCP URL to your Cursor MCP config. A ready-to-copy example is inexamples/mcp/cursor-mcp.json.

Claude remote MCP connectors are added from the UI, not throughclaude_desktop_config.json. Use the hosted URLhttps://mcp.ticketlens.com/inSettings > Connectors, or follow the short guide inexamples/mcp/claude-connector.md.

OpenClaw users can integrate TicketLens quickly by adding a workspace skill that calls the public TicketLens REST API. Start fromexamples/openclaw/skills/ticketlens-api/SKILL.md.

Seeexamples/openclaw/README.mdfor the recommended API path and notes about the more advanced MCP route.

- Base URL:https://api.ticketlens.com/v1
- OpenAPI JSON:https://api.ticketlens.com/v1/openapi.json
- Swagger UI:https://api.ticketlens.com/v1/docs
- ReDoc:https://api.ticketlens.com/v1/redoc
- Committed artifact:openapi/ticketlens-tour-search-api.v1.json

curl -sS https://api.ticketlens.com/v1/search/pois \ -H 'content-type: application/json' \ -d '{ "query": "Eiffel Tower", "city": "Paris", "language": "en", "limit": 5 }'

curl -sS https://api.ticketlens.com/v1/search/tours \ -H 'content-type: application/json' \ -d '{ "query": "ticket", "poi": { "id": "660851", "match_mode": "exact" }, "city": "Paris", "languages": ["en"], "per_page": 5 }'

For destination-specific ticketing flows like the Eiffel Tower, this is useful for agents because TicketLens can surface inventory from the official Eiffel Tower site, including hard-to-find high-season availability when it exists, alongside second-market ticket options in the same search flow.

To filter for travel dates, add adatesobject with ISOYYYY-MM-DDvalues:

curl -sS https://api.ticketlens.com/v1/search/tours \ -H 'content-type: application/json' \ -d '{ "query": "ticket", "poi": { "id": "660851", "match_mode": "exact" }, "city": "Paris", "dates": { "from_date": "2026-05-15", "to_date": "2026-05-17" }, "languages": ["en"], "per_page": 5 }'

- Usedates.from_datefor a single-day search.
- Use bothdates.from_dateanddates.to_datefor a date range.
- Dates must use ISOYYYY-MM-DD.
- dates.flexible_daysexists in the schema but is not implemented in the current public version.

submit_feedbackis available on the hosted MCP server only. It is not part of the public REST API or the OpenAPI document.

Usesubmit_feedbackwhen an agent encounters:

- broken behavior
- confusing or incomplete results
- missing capabilities
- documentation gaps
- clear product or tool improvements

- required:category,message
- optional:suggestion,related_tool_name,related_request_id,expected_behavior,actual_behavior,reproduction_summary

- bug_report
- improvement
- missing_capability
- documentation_gap
- other

{ "category": "improvement", "message": "Add clearer filter explanations when date constraints remove all results.", "related_tool_name": "search_tours", "suggestion": "Return a short hint explaining which filter removed the result set." }

{ "category": "documentation_gap", "message": "The MCP docs should explain when search_pois is recommended before search_tours.", "related_tool_name": "search_pois", "suggestion": "Add a short POI-first workflow example to the MCP quickstart." }

{ "category": "bug_report", "message": "The tool rejected a valid POI filter after resolving the POI successfully.", "related_tool_name": "search_tours", "related_request_id": "req-123", "expected_behavior": "The search should accept the resolved POI and return matching experiences.", "actual_behavior": "The tool returned an invalid argument error.", "reproduction_summary": "Resolve a POI with search_pois, then pass the returned POI id into search_tours." }

examples/api/curl/eiffel-tower-ticket-search.sh

examples/api/curl/hop-on-hop-off-search.sh

examples/api/curl/football-ticket-search.sh

- examples/api/javascript/search_experiences.mjs
- examples/api/python/search_experiences.py

Perform web, news, and image searches using the Microsoft Bing Search API.