Skip to main content

Sitata MCP for Developers

Sitata runs an MCP (Model Context Protocol) server for developers. Connect it to the AI coding assistant you already use (Claude, Cursor, VS Code / GitHub Copilot and other MCP clients) and the assistant can read these docs and the API reference, walk you through an integration step by step, and make live calls to your staging account so you can try things as you build.

https://mcp.sitata.com/mcp
Staging only

The developer MCP server only ever talks to Sitata's staging environment. It can't see or change production data, which makes it safe to experiment with. Staging deliveries are still real, though: webhooks reach the URLs you register, and assistance issues you open reach Sitata's staging team. Never use it for a real emergency, and never give it a production token.

What you need

  • Nothing, for the docs, guides and API reference tools. They work without credentials.
  • Your staging credentials, for live calls. In the staging partner portal, copy your organization token and company id from the API page. They're sent as two headers:
X-Sitata-Api-Key: <your staging organization token>
X-Sitata-Company-Id: <your staging company id>

Authorization: Bearer <token> is accepted in place of X-Sitata-Api-Key.

No staging account yet? Ask your assistant to apply for you (the start_partner_application tool), or contact us.

Connect your AI tool

The server speaks MCP's remote Streamable HTTP transport. Each tool below takes the same URL and headers; keep your token in an environment variable or a secret prompt rather than in a file you commit.

Claude Code

claude mcp add --transport http sitata https://mcp.sitata.com/mcp \
--header "X-Sitata-Api-Key: $SITATA_STAGING_TOKEN" \
--header "X-Sitata-Company-Id: $SITATA_STAGING_COMPANY_ID"

Leave out the two --header lines to use the docs and reference tools only.

Claude Desktop

For docs and reference only, add a custom connector (Settings โ†’ Connectors โ†’ Add custom connector) with the URL https://mcp.sitata.com/mcp.

To send your staging headers as well, add the server to claude_desktop_config.json through the mcp-remote bridge (needs Node.js):

{
"mcpServers": {
"sitata": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.sitata.com/mcp",
"--header", "X-Sitata-Api-Key:${SITATA_STAGING_TOKEN}",
"--header", "X-Sitata-Company-Id:${SITATA_STAGING_COMPANY_ID}"
],
"env": {
"SITATA_STAGING_TOKEN": "<your staging organization token>",
"SITATA_STAGING_COMPANY_ID": "<your staging company id>"
}
}
}
}

Cursor

In ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

{
"mcpServers": {
"sitata": {
"url": "https://mcp.sitata.com/mcp",
"headers": {
"X-Sitata-Api-Key": "<your staging organization token>",
"X-Sitata-Company-Id": "<your staging company id>"
}
}
}
}

VS Code (GitHub Copilot)

In .vscode/mcp.json. VS Code asks for the values the first time and stores them securely:

{
"inputs": [
{ "type": "promptString", "id": "sitata-token", "description": "Sitata staging organization token", "password": true },
{ "type": "promptString", "id": "sitata-company", "description": "Sitata staging company id" }
],
"servers": {
"sitata": {
"type": "http",
"url": "https://mcp.sitata.com/mcp",
"headers": {
"X-Sitata-Api-Key": "${input:sitata-token}",
"X-Sitata-Company-Id": "${input:sitata-company}"
}
}
}
}

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP works: give it the URL and, for live calls, the two headers. Once connected, ask your assistant to run verify_connection to check your staging credentials.

Running it locally

The same server can also run on your machine over stdio, with your staging credentials in the SITATA_STAGING_API_KEY and SITATA_STAGING_COMPANY_ID environment variables. Most teams won't need this; if your tooling only supports local servers, contact us for the build.

What it can do

AreaTools
Guides & docsget_integration_guide, search_docs, read_doc, list_docs
API referencesearch_api_reference, describe_endpoint
Connectionverify_connection
Onboardingstart_partner_application, get_partner_application_status
Insurancelist_products, quote_products, purchase_policy, list_policies, get_policy
Travellerscreate_traveller
Assistance & chatcreate_assistance_issue, list_assistance_issues, get_assistance_issue, send_chat_message, list_chat_messages
Claimslist_claims, get_claim
Webhookslist_webhook_endpoints, create_webhook_endpoint, list_webhook_events
Certificationget_certification_status, list_certification_submissions, create_certification_submission, submit_certification_submission
Anything elsecall_staging_api: any documented staging endpoint (admin endpoints excluded)

The guides, docs and reference tools need no credentials; everything else calls your staging account.

Integration guides and prompts

get_integration_guide returns a step-by-step plan that ties the relevant docs pages, endpoints and tools together. Clients that show MCP prompts (often as slash commands) also list one prompt per guide:

PromptCovers
integrate_getting_startedStaging access, credentials and your first API call
integrate_insuranceEmbedded insurance: list products, quote, purchase, refunds and changes
integrate_assistance_issuesCreate and track assistance cases for your travellers
integrate_emergency_chat24/7 emergency assistance chat in your app
integrate_claimsClaims widget, claims API and claim webhooks
integrate_webhooksReceive Sitata events (sales, claims, alerts) on your servers
integrate_certificationGet your marketing materials and purchase flow approved
integrate_go_liveEverything that must be true before you switch to production

Things to try

  • "Walk me through quoting and selling travel insurance, and run a quote on staging for two travellers going to Spain next month."
  • "How do I add emergency chat to our app? Create a test traveller and open an assistance issue for them."
  • "Register https://example.com/hooks for claim events and show me the payload I'll receive."
  • "Which endpoint changes a policy after purchase, and what does its request body look like?"

Ask Sitata AI

Prefer not to set anything up? Ask Sitata AI is a chat assistant with the same tools, available as a chat button on Sitata's developer pages and in the partner portal. In the partner portal it uses your staging credentials automatically; elsewhere, open the key icon in the chat panel to add your staging organization token and company id. They're kept in that browser tab only.

Limits

  • Staging only. Nothing the server does reaches production. When you're ready to launch, follow the pre-launch checklist and switch your own integration to production credentials.
  • No admin endpoints. call_staging_api can call any documented partner endpoint, but Sitata admin endpoints are blocked.
  • Your organization only. Calls run as your staging organization, with the same permissions as your staging token.
  • Ask Sitata AI is rate-limited to about 20 messages a minute.
  • AI assistants make mistakes. Treat their output as a starting point and check it against the docs and the API reference.

For acting on behalf of a signed-in traveller in production (coverage questions, claims, buying a policy), see the traveller MCP server.