Travel Protect MCP Server
Introduction
The Travel Protect MCP server lets your AI assistant fetch live travel insurance quotes from Travel Protect. It uses the Model Context Protocol (MCP), an open standard that allows AI assistants such as Claude and ChatGPT to call external tools. Once connected, you can ask your assistant for single-trip or annual multi-trip quotes in plain language, compare cover levels, and receive a direct purchase link — without leaving the conversation.
What You Can Do
The server exposes two tools to your assistant:
- Get travel insurance quotes — request a quote for a one-off trip (
SINGLE) or annual multi-trip cover (MULTI), based on travel dates, destinations, and traveller ages. The response includes available products, benefits, pricing, and a purchase URL. - Check service health — confirm that the upstream Travel Protect quote API is reachable, which is useful when debugging a connection.
Availability: Travel Protect travel insurance quotes are only available to Australian citizens and permanent residents. The MCP server returns quotes in AUD and policies are issued under Australian regulations.
Before You Start
To use the Travel Protect MCP server, you’ll need:
- An AI assistant that supports MCP servers or custom connectors, such as Claude (web or desktop), Claude Code, or ChatGPT.
- No account, API key, or sign-in is required — the server is public and uses no authentication.
Note: Some assistants restrict custom connectors to paid plans. For example, custom connectors in Claude and ChatGPT are currently only available to users on paid plans. Check your assistant’s documentation for current availability.
Server URL
All clients connect to the same endpoint over Streamable HTTP:
https://anthropic-mcp-tp-prod-1028024735931.australia-southeast1.run.app/mcp
Claude (Web & Desktop)
This is the easiest and recommended way to connect. Custom connectors are available on the web and desktop versions of Claude.
- Open Claude (web or desktop).
- Go to Settings → Connectors.
- Click Add custom connector.
- Enter a name (for example, Travel Protect Insurance) and paste the server URL:
https://anthropic-mcp-tp-prod-1028024735931.australia-southeast1.run.app/mcp - Click Add. No sign-in is required.
- In a new chat, open the Search and tools menu near the prompt and make sure the connector is enabled.
Claude Desktop (Config File)
If you prefer to manage MCP servers through Claude Desktop’s configuration file, you can register the server manually.
- Open Claude Desktop settings:
- On Windows, use the keyboard shortcut
Ctrl + , - On macOS, use the keyboard shortcut
Command + ,
- On Windows, use the keyboard shortcut
- Navigate to the Developer tab.
- Click Edit Config and add the following configuration:
{ "mcpServers": { "travel-protect-insurance": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://anthropic-mcp-tp-prod-1028024735931.australia-southeast1.run.app/mcp" ] } } } - Save the file and restart Claude Desktop.
Note: The config-file method runs the server through mcp-remote, which requires Node.js 22.16 or later with npm. If you don’t have Node.js installed, download it from nodejs.org — or use the custom connector method above, which has no prerequisites.
Claude Code
Run the following command in your terminal:
claude mcp add --transport http travel-protect-insurance
https://anthropic-mcp-tp-prod-1028024735931.australia-southeast1.run.app/mcpFor more information, see the Claude Code MCP documentation.
ChatGPT
ChatGPT supports custom MCP connectors through developer mode, which is currently available on ChatGPT paid plans.
- Open ChatGPT (web or desktop).
- Go to Settings → Connectors → Advanced and enable Developer mode.
- Back in Connectors, click Create and enter:
- Name: Travel Protect Insurance
- MCP server URL:
https://anthropic-mcp-tp-prod-1028024735931.australia-southeast1.run.app/mcp - Authentication: No authentication
- Save the connector. In a new chat, enable it from the tools menu.
For more information, see the ChatGPT connectors documentation.
Check the Connection
To confirm the Travel Protect MCP server is working:
- Look for the connector in your assistant’s tools menu. In Claude, it appears in the Search and tools menu near the prompt.
- Ask a simple question to test the connection. For example:
Check whether the Travel Protect travel insurance service is up.
Your assistant should ask permission to run the check_api_health tool. Approve it and wait for the response — a healthy reply confirms the connection end to end.
get_travel_insurance_quote
Fetches travel insurance quotes from the Travel Protect public quote API. Use SINGLE for a one-off trip or MULTI for annual multi-trip cover.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
quote_type | string | Yes | SINGLE for a one-off trip, MULTI for an annual multi-trip policy. |
cover_start_date | string | Yes | Coverage start date in YYYY-MM-DD format. Must be a future date. |
cover_end_date | string | Conditional | Coverage end date in YYYY-MM-DD format. Required for SINGLE trips; calculated automatically for MULTI. |
destinations | array | Yes | Destination countries as ISO alpha-2 codes, e.g. IT, GR, JP. |
travellers | array | Yes | Ages of all travellers, e.g. 26, 30, 12. Ages must be 0–100. |
Response
Returns the available products with cover levels, benefits, pricing in AUD, and a purchase URL that takes you to the Travel Protect website to complete the policy.
check_api_health
Checks whether the upstream Travel Protect quote API is reachable. Takes no parameters and returns the current service status. If quote requests are failing, ask your assistant to run this tool first to rule out a service outage.
Example Prompts
Once connected, try asking your assistant:
- “Get me a travel insurance quote for two travellers aged 32 and 29, going to Japan from 10 to 24 September.”
- “I travel overseas four or five times a year — quote me an annual multi-trip policy starting next month. I’m 41.”
- “Compare single-trip cover for a family of four (ages 38, 36, 9, 6) visiting Italy and Greece for three weeks in December.”
- “Is the Travel Protect quote service up right now?”
Troubleshooting
The connector doesn’t appear in my assistant
- Confirm the server URL was entered exactly, including the
/mcppath. - Custom connectors may require a paid plan on your assistant (see Before You Start).
- On Claude Desktop with the config-file method, check that Node.js 22.16+ is installed and restart the app after editing the config.
The assistant connects but doesn’t use the tools
- Make sure the connector is enabled in the chat’s tools menu — some assistants require you to switch tools on per conversation.
- Be explicit in your prompt, e.g. “Use the Travel Protect travel insurance tool to quote…”.
- Approve the tool-use permission prompt when your assistant asks.
Quote requests return an error
- “Cover start date must be in the future” — dates must be upcoming, in
YYYY-MM-DDformat. - “Invalid country code” — destinations must be ISO alpha-2 codes (e.g.
JP, notJPN). Your assistant usually handles this; rephrase with the full country name if it doesn’t. - Missing end date —
SINGLEquotes need both a start and end date. - If parameters look correct, ask your assistant to run
check_api_healthto rule out a service outage.
I’m outside Australia
- Travel Protect policies are only available to Australian citizens and permanent residents departing from Australia. Quotes returned to other residents are not purchasable.
Privacy & Data
- The server requires no authentication and holds no account data.
- Quote requests send only the trip details your assistant provides: trip type, dates, destination codes, and traveller ages. No names, contact details, or payment information pass through the MCP server.
- Purchases are never completed by the assistant — the quote includes a purchase URL, and payment happens on the Travel Protect website.
- See our privacy policy and terms of use.
Support
If you’re stuck or something looks wrong, email us at hello@travelprotect.au with the assistant you’re using, the prompt you tried, and any error message shown. You can also reach us through the contact page.
Developers integrating directly with the underlying API can find the full reference at travelprotect.au/developers/api-docs.
