Overview

Model Context Protocol (MCP) is an open standard that lets AI agents call tools hosted by other services. In plain terms: you point Claude (or Cursor, or any other MCP client) at our MCP server, and from that point forward you can ask questions like "pull Apex Plumbing's full carrier history" or "show me Pinnacol's 1/1/2026 Colorado filings" and the agent retrieves the data live, reasons on it, and writes it up for you.

It's the fastest way to turn your Insurance Xdate data into research, call lists, and leave-behinds without having to click through the web app for every lookup. (said Claude)

Setup

• https://insurancexdate.com/settings.php#api - create API key here
• https://www.insurancexdate.com/settings.php#xchange - add funds here
• An MCP-capable AI client installed locally. Claude Desktop, Claude Code, Cursor, and LM Studio are all supported.

Connect your AI client

MCP server configuration (JSON) 

Or you can do it - add the following to your AI client's MCP configuration. In most clients this is a JSON file (for example claude_desktop_config.json, .cursor/mcp.json), or a "Connectors / MCP" section in the settings UI.

{
 "mcpServers": {
   "insurancexdate": {
     "url": "https://www.insurancexdate.com/api2/McpData",
     "headers": {
       "X-API-KEY": "YOUR_API_KEY"
     }
   }
 }
}

This information is found under the Setup tab. 

OAuth Authentication

You can also set up with OAuth authentication. In Claude it is a custom connector. Click the + button and add the url to the url field and name it.

Claude Code shortcut

In Claude Code you can skip editing the JSON by hand. After creating your API key, run (on one line):

claude mcp add --transport http --scope user insurancexdate \

 https://www.insurancexdate.com/api2/McpData \

 --header "X-API-KEY: YOUR_API_KEY"

You can also have it grab it using their chrome extension as the key is not part of your actual chat conversation.

Then quit and relaunch Claude Code (or run /exit and reopen) so it picks up the new server. You'll see the insurancexdate tools appear in the tools list once it reconnects.

Available tools and pricing

Cost is deducted from your prepaid balance as tools are called. Balance and per-tool usage are visible on the Settings page under the Pricing Tab. 

On your AI client side you can set paid tools as requiring permission and free tools as always allowed to prevent unnecessary spend. 

Note: Data field availability varies by state. See the State Data Availability KB article for specifics on what's returned where.

Example Workflows 

Provide Context

The tools are designed to layer. 

Prospects for drop-in near my Appt

Note that I pulled a random company (Apex Plumbing) but you could say something like Find 10 businesses near my appointment this afternoon renewing in the next 60-90 days…

At the time Design wasn't part of the desktop app so it created an acceptable html file for print. That's no longer the case, but even without design it will make it pretty. Simply have it create a brand-skill based on your existing content to come up with a good reusable format. 

What it cost

search, filter: free (used several times)

company_details on Apex + 5 prospects: 6 x $0.25 = $1.50

serff_search: $0.05

serff_filing: $0.10

Total session: $1.65

Output: a qualified 5-account prospect list with rate-shock context and a printable flyer for the hottest lead — all from one conversation.

Cost and workflow tips

Start free, then drill in. Always use search/filter to narrow before calling company_details. A sloppy search wastes $0.25 per misfire.

One key per client. If you run multiple MCP clients (say Claude Desktop at home and Claude Code at work), create a separate key for each. Makes it obvious where usage is coming from, and you can rotate or revoke one without breaking the other.

Cache in the conversation. The AI client keeps its conversation context, so a second question about the same company doesn't need another company_details call. Anchor to one lookup, then ask multiple follow-ups in the same chat.

Use talkpoints selectively. talkpoints adds prospecting angles but it's $0.10 per call. Save it for accounts you're actually going to reach out to — not for browsing. Considering full history is provided, your AI client can probably make their own.

Common questions

Which AI clients work with this?

Any client that speaks MCP. We've tested Claude Desktop, Claude Code, Cursor, and LM Studio. If your client supports custom MCP servers with HTTP transport and a custom auth header, it'll work.

Does the MCP have access to everything my web login has?

It accesses the same underlying dataset, scoped by the permissions associated with your API key. Tools like company_details return the same data you'd see by opening a company page in the web app.

Can I use the same API key for the REST API and the MCP?

Yes. The key authenticates you against both surfaces. If you're building a script that calls the REST endpoints directly (not via MCP), use the same X-API-KEY header.

What happens if my balance hits zero?

Paid tool calls (company_details, talkpoints, serff_search, serff_filing) will start failing with an insufficient-balance error. Free tools (search, filter) continue to work. Add funds from the Settings page and calls resume immediately.

How is this different from using the REST API directly?

Same data, same pricing. The MCP is just the AI-friendly front door — it lets an LLM call the tools conversationally and chain them together. If you're writing scripts or building your own integrations, call the REST API. If you're doing research, prospecting, or ad-hoc analysis in an AI chat, use the MCP.