Skip to main content

Connect an AI Assistant for Your Travellers

Sitata's traveller MCP server lets an AI assistant act for one signed-in traveller: explain what their policy covers, answer questions from its wording, file and follow a claim, manage their trips, and quote and pay for a new policy. It works with any assistant that supports remote MCP servers with OAuth, such as Claude or ChatGPT, and with an AI agent you build yourself.

https://mcp.sitata.com/traveller/mcp
New

The traveller MCP server is new. Contact us with feedback, or if you'd like help connecting your own AI agent.

Unlike the developer MCP server, which only touches staging, this server works with the traveller's real policies, claims and payments.

How travellers connect

The server uses OAuth 2.1, with Sitata as the authorization server. The traveller never shares a password or API key with the assistant:

  1. The traveller adds the server URL to their AI assistant (for example as a custom connector).
  2. The assistant sends them to Sitata to sign in, with an email PIN or their policy number. Only traveller accounts can connect.
  3. Sitata shows a consent page naming the app and what it is asking to do. The traveller approves or declines.
  4. The assistant receives a short-lived access token for those permissions only. It is refreshed automatically while the connection lasts.

Assistants discover all of this on their own: the server's /.well-known/oauth-protected-resource metadata points to Sitata, which publishes standard authorization server metadata, supports dynamic client registration and requires PKCE.

Permissions (scopes)

ScopeShown to the traveller asLets the assistant
coverage:readSee your policies, what they cover, and your claimsList their policies, read benefits, limits, excesses and policy documents, download their certificate of insurance, and see their claims
claims:writeStart, fill in and submit claims for youOpen a draft claim, save answers, attach files, submit, reopen or withdraw a claim, and provide bank details when the insurer asks for them
purchaseGet insurance quotes and payment links for youFind products for a trip, get a firm quote, and create a link to Sitata's payment page
tripsSee, add, change and delete your tripsList, create, update and delete their trips, and look up a country's entry requirements

A connected assistant can only reach what its scopes allow. It can never see the traveller's Sitata login token, create other tokens, or reach any partner or admin feature.

What an assistant can do

Coverage and policy wording

The assistant can list the traveller's policies (dates, status, products, insurer and assistance contacts) and explain a policy's benefits, limits, excesses and exclusions. It can also list the policy documents, read their full text (the policy wording, terms and similar) so it can quote them in its answers, and fetch the latest certificate of insurance.

Claims

The assistant can take a traveller through a claim from start to finish:

  1. Open a draft claim on a policy and get its questions.
  2. Save the traveller's answers and the amount claimed. Nothing goes to the insurer while the claim is a draft.
  3. Attach supporting files (up to 10 MB each). Usually the assistant gives the traveller a link to a secure upload page, valid for 24 hours, where they add receipts and reports themselves; it can also attach a file it was given.
  4. Submit the claim.
  5. Follow it afterwards: status, and any documents the insurer has asked for. Before the insurer starts its review, the claim can be reopened to change answers or add files, then submitted again.
  6. When the insurer asks for bank details to pay the claim, send them.

Steps that can't be undone or that move money need the traveller's explicit agreement. Submitting or withdrawing a claim and sending or confirming bank details all work in two calls: the first returns a summary for the assistant to show the traveller, and only a second call with confirm: true, made after the traveller says yes, carries out the action.

Buying a policy

The assistant can find the products available for a trip, with prices, and get a firm quote for the traveller's choice, including the total to pay. To quote, it needs:

  • the trip's dates, where the travellers live, and each country they'll visit with the dates spent there;
  • the policy holder, who must be travelling: name, date of birth and email. The policy is sent to that email, and a Sitata account is created for them if they don't have one;
  • everyone else on the trip (up to 9), covered under the same policy: name, date of birth and how they're related to the policy holder. No email is needed for them;
  • the trip cost, for products priced on it, such as cancellation cover.

The assistant never handles card details. Payment happens on Sitata's own secure payment page: the assistant shows the traveller the total and, once they confirm, gives them a payment link, valid for 24 hours. The policy is issued once they pay there.

Trips

With the trips scope, the assistant can list the traveller's trips, add a new one (so they get Sitata's alerts and advice for it), change its dates or destinations, and delete it, which needs the traveller's confirmation. It can also look up what they need to enter a country: visa, passport validity and required forms or certificates, with links to the official sources. This is information, not immigration advice.

For partners: your own AI agent

If you build your own AI agent for your customers, it can connect to the traveller server like any other MCP client, and your customers sign in and consent in the same way.

To have policies sold through your agent attributed to your organization, pass organization_id when finding products and quoting (find_products and get_quote). Its value is your company id, or your affiliate id. Sitata only honours it for organizations that sell Sitata products for commission; without it, the sale is recorded as a direct Sitata sale.

Sitata can also bind your agent's OAuth client to your organization. Every sale through it is then attributed to you automatically, whatever organization_id the agent sends, and its API calls count toward your organization's API usage. Contact us with your agent's client_id to have it bound. Once it is, the partner portal lists it under Settings โ†’ AI agents, with whether it is active and how many travellers currently have it connected.

Disconnecting an app

A connection lasts until it is disconnected or goes unused for 30 days. Travellers can remove the connector in their AI assistant at any time, or disconnect it from Sitata: every assistant they've connected, with the permissions they gave it, is listed in the Sitata web app under Settings โ†’ Connected apps, and in the Sitata mobile app under Settings โ†’ Privacy โ†’ Connected apps. Disconnecting there immediately revokes everything that app holds for them; they can connect it again later from the assistant.

Information, not advice

Assistants are instructed to answer from the policy's own wording, to name the document an answer comes from, and to say when the wording is unclear or silent rather than guess. When it describes products, it does so from their own wording, not as a recommendation. Its answers are information, not advice: the policy documents are what count, and the insurer decides every claim.

In an emergency, the traveller should contact local emergency services and the assistance number on their policy, not an AI assistant.