WebMCP for Tour Operators: Your Booking Engine Just Became an API for AI

In August 2026, WebMCP tools went live in the ChatGPT desktop browser and Codex, weeks after Shopify enabled the protocol across every Liquid storefront. The practical effect: a website can now hand an AI agent a small, safe set of tools — and the agent will use them instead of scraping pages and guessing at buttons.

For tour operators this is the difference between being described and being booked. An agent that can call check_availability('sunset-kayak', '2026-09-04', 2) and get a structured answer doesn't abandon the task the way page-scraping agents do when they hit a JavaScript calendar widget.

You don't need to rebuild your booking engine. Most operators sit on top of a reservation platform that already has an API. WebMCP is a thin declaration layer: a manifest that says 'here are the three things an agent may do here, and here's the endpoint for each.' Start with read-only availability, add booking once you trust the traffic.

Our scanner checks for a WebMCP manifest, MCP discovery documents, A2A agent cards and OpenAPI specs — the four ways agents currently discover site capabilities. Scoring even one of them puts you ahead of roughly nine in ten operator sites we've scanned.