This is an early server and the vendor says so plainly in its own tool table: the company profile answers today, and search, destinations, fixtures, tour modules and enquiry submission are labelled coming soon. What it establishes now is the connection — no key, no install — so the tools become available to a client that is already pointed at it.
The public endpoint of Follow On Tours, a bespoke cricket travel broker. It is read-only apart from a rate-limited enquiry submission, and needs no authentication at all — any client that speaks Streamable HTTP can connect to it.
- An account of who Follow On Tours are and how they work
- Cricket tours searched by destination, dates, series or format — the tool table marks this one coming soon
- Destination guides covering hotels, venues, transfers and visas — marked coming soon
- Upcoming fixtures with dates, venues and availability — marked coming soon
- Pre-built tour modules for Australia and other destinations — marked coming soon
- A qualified travel enquiry submitted for a bespoke proposal — marked coming soon
Nothing but the URL: https://www.followontours.com/api/mcp, over Streamable HTTP. No account, no key. Claude.ai takes it as a custom connector; desktop clients take it as a url entry.
One command — npx -y mcp-remote https://www.followontours.com/api/mcp