Skip to main content
The AI Insurance MCP connector lets you work with your AI Insurance data from Claude. In a conversation, you can ask Claude to look up a submission, summarize a policy’s endorsement history, bind a prepared quote, create a task, or draft a note on a claim, and Claude does it against your live AI Insurance account. It’s built on the Model Context Protocol (MCP), an open standard for connecting AI assistants to external systems. You add AI Insurance as a custom connector in Claude.ai or Claude Desktop, sign in once with your normal AI Insurance account, and Claude can call the same REST API you can, acting as you, with exactly the permissions your user has.
The MCP connector has not been released yet. This page documents the connector ahead of its launch. The connector URL below will not accept connections until the rollout completes. Watch the changelog for the release announcement.
The MCP connector is in beta. Once released, it may need to be enabled for your company before the connector will accept connections. If you can’t connect, reach out via the support portal or your AI Insurance contact to get access.

Adding the connector

The connector URL is:
1

Open your Claude connector settings

In Claude.ai, go to Settings → Connectors and choose Add custom connector. In Claude Desktop, the same option lives under Settings → Connectors. (Custom connectors require a Claude plan that supports them; see Claude’s own documentation for plan availability.)
2

Enter the connector URL

Give the connector a name (for example, “AI Insurance”) and paste the URL https://mcp.go.aiinsurance.io/mcp. No API key or other credentials are entered here. Authentication happens in the next step.
3

Sign in with your AI Insurance account

The first time you connect, a browser window opens asking you to sign in to AI Insurance. Use the same account you use for the web app at go.aiinsurance.io. Once you approve, Claude is connected. You won’t need to sign in again unless your session expires or you disconnect.
4

Try it out

Start a conversation and ask something like “Which AI Insurance companies can I access?” or “Find the submission for Acme Manufacturing and summarize where it stands.”

How access and permissions work

The connector acts on your behalf:
  • You sign in as yourself. There are no shared credentials and no API keys. Each user connects with their own AI Insurance login.
  • Claude can do what you can do, no more. Every request is checked against your user’s role and permissions, per company, exactly as in the web app and the REST API. If your role can’t delete quotes, Claude can’t either.
  • Multi-company users pick a company. If your account spans several companies, Claude first lists the companies you belong to, with your role in each, and works within the one you choose.
  • Everything is logged. Actions taken through the connector are recorded in the same audit log as other API activity.
The connector leaves out the operations that wipe a whole company’s data and the operations reserved for AI Insurance staff.
Claude’s writes are real. When you ask Claude to create, update, or delete a record through the connector, it changes your live data, the same as making the edit in the app. Claude treats a clear, specific request as confirmation to proceed, so be deliberate when asking for deletions or bulk changes.

What Claude can do

The connector has seven tools. Four of them let Claude use any operation of the REST API that your role permits, so Claude can work with records, policies, quotes, claims, tasks, notes, files, forms, financials, and your company’s configuration without a separate tool for each. Two more let Claude read this documentation, so it can answer how AI Insurance works, not only what your records hold. Claude picks the operation itself. For “add a note to the Acme claim”, it searches for a note operation, reads how that operation works, and then calls it with write_api. Each call is the API operation you could make yourself, so the API reference documents what it does, what it needs, and what it returns. Records are generic and their fields differ per company. Claims and incidents are event records, and insureds are exposure records. The other record types are submission, quote, person, and organization. Policies, tasks, notes, files, forms, financials, and configuration have their own operations.

Changing your configuration

The fields, option sets, custom objects, and page layouts that define how your app works are reachable the same way. Claude reads your configuration with read_api and changes it with write_api. These operations need a role that holds the configuration permissions, such as Admin (see Configuration Management). The configuration patch operation supports a dry run, which checks the full result without committing anything, and Claude can run it before it commits a change.

Tips for good results

  • Be specific about records. “Delete the duplicate exposure for 123 Main St” works better than “clean up the exposures”. Claude confirms with you when a request is ambiguous or implies a bulk change.
  • Let Claude read the fields before writing. For creates and updates, Claude asks describe_api for the fields your company configures, so the data it writes matches your setup. If a value is rejected, the error names the exact field so it can fix and retry.
  • Ask for less when a result is large. A response over about 60,000 characters is cut, and Claude is told to retry with a smaller page size or a filter. Naming the record or date range you care about saves that retry.

Troubleshooting