Wigoo
Wigoo is an AI travel companion. Today: travel eSIMs for 190+ countries and regions, with networks, data, validity and prices in 55 currencies, plus a link to buy. Trip planning and more travel services are coming to the same server. Read only, no sign-in.
Hosted MCP Server
npx add-mcp 'https://api.getwigoo.com/api/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
MCP server (/mcp)
Wigoo sells travel eSIMs. The Wigoo MCP server lets an AI assistant read the same catalog the website shows, so it can answer with real plans and prices instead of guessing, and give the traveler a link that opens the purchase of exactly one plan.
https://api.getwigoo.com/api/mcp
It is a server for the Model Context Protocol, the open standard that lets assistants such as Claude and ChatGPT use outside tools. It speaks Streamable HTTP, needs no API key and no sign in, and keeps no session.
What an assistant can do
| Tool | What it returns |
|---|---|
search_destinations | Countries and regions Wigoo sells eSIMs for, with the starting price, the networks and a buy link |
get_destination | What one destination offers: data sizes, validity options, unlimited day passes, top ups |
list_plans | Every plan on sale for a destination, with data, validity, networks and price |
get_quote | The price of one plan, a link that opens its purchase, and the steps to buy without an account |
All four tools are read-only. Prices come back in the currency the traveler pays in, converted the way the website converts them.
What it does not do
- It does not place orders. The purchase happens on getwigoo.com, through the link from
get_quote. Orders paid inside the assistant are planned, not available. - It cannot see an account. There is no sign in, so there is nothing about a customer to read: no eSIMs, no credit, no saved cards.
- It does not charge anything. A quote is a list price. The server calculates the real amount again at checkout.
How the pieces fit
Step 1: The assistant finds the plan
It calls search_destinations, then list_plans or get_destination, and compares plans for the trip.
Step 2: It asks for a quote
get_quote returns the price in the traveler's currency and a buy_url: the plan link.
Step 3: The traveler buys on the website
The link opens the destination page on that plan, already selected, and Buy opens the purchase. An email and a payment are enough, with no account. The eSIM QR code appears right after payment and arrives by email.
Where to go next
- Quickstart: Connect Claude, Claude Code, ChatGPT or any MCP client and make the first call.
- Tool reference: Parameters, response fields and examples for the four tools.
- Protocol and limits: Transport, protocol versions, capabilities and rate limits.
- Rules for agents: What to ask the traveler before paying, and what to keep in the links.
- Add eSIMs to your AI travel app: Building your own app? How to wire the server, when to offer an eSIM and what to check before you ship.
- Call the server from your code: Examples for the Vercel AI SDK, the OpenAI Responses API and the Anthropic Messages API.
- Hand the traveler to checkout: What your app does with the buy link, and what never to do.
What changed and when is in the changelog. Short answers are in the FAQ.