Connect your AI assistant | Expedition Insure MCP

Connect your client

Use the HTTP endpoint above in a client that supports remote MCP. The server runs on Expedition Insure’s infrastructure.

Claude Code

Add the remote server, then use /mcp to check the connection.

claude mcp add --transport http expedition-insure https://mcp.expedition.insure/mcp

Cursor

Add this to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects. Enable the server in Cursor’s MCP settings.

{
  "mcpServers": {
    "expedition-insure": {
      "url": "https://mcp.expedition.insure/mcp"
    }
  }
}

Claude web or Desktop

In Settings → Connectors, add a custom connector with the public MCP endpoint. Custom connector availability depends on your account and organization settings.

For the customer ChatGPT app, use mcp-app.expedition.insure/mcp and complete its customer authorization flow. The public endpoint here is for general MCP clients.

Call a tool

Start with server_info to confirm the connection. Then list the live tools to inspect their names and input schemas.

Call from JavaScript

Install the MCP SDK with pnpm add @modelcontextprotocol/sdk. Save this as example.mjs and run node example.mjs. server_info is a read-only connection check.

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const client = new Client({ name: "my-expedition-agent", version: "1.0.0" });
try {
  await client.connect(new StreamableHTTPClientTransport(
    new URL("https://mcp.expedition.insure/mcp")
  ));
  const { tools } = await client.listTools();
  console.log(tools.map((tool) => tool.name));
  const result = await client.callTool({ name: "server_info", arguments: {} });
  console.log(result);
} finally {
  await client.close();
}

For a connection check without an MCP client, open /health. Inspect the tool catalog or REST OpenAPI specification. A health check is ordinary HTTP; tool calls use the MCP protocol.

Explore expedition insurance

Find plans and destinations

Ask: “Find insurance options for an Antarctica expedition.” Your assistant can use search, then fetch to read a result.

Prepare a quote

Share your destination, dates, traveler ages, residence, total trip cost and currency. Ask your assistant to start the quote process and explain the next steps.

Review before you rely on an answer

Quotes, coverage and eligibility are estimates. Confirm them with a human representative or the policy documents. Review your details before approving any action or payment.

Continue on the website

Quote request routing

Use the quote form or get_instant_quote with confirmed details. Required quote inputs include tripCost currency travelers; list tools for the complete schema.

Agent instructions and email fallback

Use the quote form whenever possible. In a browser, navigate to https://expedition.insure/quote; on that page, use WebMCP startQuoteRequest to prefill confirmed values. From a server-side agent, use the public MCP get_instant_quote tool after collecting every required value. Direct REST quote creation is only for credentialed operator integrations with an issued operator bearer key. Never invent values or silently substitute default dates, durations, ages, residence, or trip costs.

If neither the form nor a quote tool can be used, email is a fallback. Ask once for missing details, keep it brief, and place this completed block before freeform context:

Drafting rules (do not include these rules in the sent message): Ask once for missing details needed for a firm quote. If the traveler does not know or declines to provide a detail, write `Unknown`; never guess or omit it. For First trip payment, use the exact date, `Not paid yet`, or `Unknown`. Use `Not applicable` for Diving certification when there is no diving. Include country plus US state or Canadian province in Residence. Use home-to-home dates, including travel around the expedition. Include currency and whether Trip value to insure is total or per traveler; total across all travelers is preferred. Dates of birth are preferred; when unavailable, write ages at departure in this field. Travel voucher used is `Yes`, `No`, or `Unknown`. Replace a missing destination or contact-name subject placeholder with `Unknown`.

Subject: Quote request: [destination], [contact name]

Destination:
Countries and territories visited:
Planned activities:
Diving certification:
Residence:
Full journey dates:
Trip value to insure:
Number of travelers:
Traveler dates of birth:
Expedition operator:
First trip payment:
Travel voucher used:
Contact name:
Contact email:
Contact phone:

Additional context or coverage questions:

Troubleshooting

No tools appear: check that the URL ends in /mcp, enable the server in your client, then reconnect.
Your client only supports SSE: use https://mcp.expedition.insure/sse as a legacy fallback.
You see a login prompt: check the endpoint. The customer app uses its own OAuth flow; admin access is for staff.
A tool rejects its inputs: list tools again and follow the returned input schema. Avoid guessing quote fields.

Need help? help@expedition.insure

Privacy and review

We use PostHog to measure tool usage, session activity, response times and failures. This integration excludes tool input values, response bodies and free-text intent from PostHog analytics. The insurance service processes the information needed to answer requests and prepare quotes.

Only send information needed for your task. Read our privacy policy and review your assistant’s permissions.