Industries10 min read

MCP Servers for Insurance: Automate Claims, Underwriting & Policy Workflows in 2026

Discover how insurance carriers, MGAs, and brokers use MCP servers to automate claims processing, underwriting decisions, policy management, and compliance workflows with AI.

By MyMCPTools Team·

The insurance industry runs on data — policy data, claims data, actuarial tables, compliance records. But most of that data is locked in siloed systems, requiring manual effort to bridge. MCP servers change this by giving AI assistants direct, structured access to the tools and databases that power insurance operations.

This guide covers the most impactful MCP server use cases for insurance carriers, managing general agents (MGAs), and independent agencies in 2026.

Why Insurance Is a Strong Fit for MCP Automation

Insurance workflows are document-heavy, data-intensive, and highly repetitive — exactly the profile where MCP-connected AI delivers the most value. The key advantages:

  • Structured data everywhere — Policy terms, coverage limits, claims history, and actuarial data have clear schemas that AI can reason over directly.
  • High-volume repetitive tasks — First notice of loss (FNOL) intake, policy renewals, endorsement requests, and coverage verification follow predictable patterns.
  • Compliance requirements create audit trails — MCP servers can log every AI action, giving compliance teams the traceability they require.
  • Customer communication volume — Insurers handle thousands of inbound inquiries; AI with context access can respond accurately without human review on routine questions.

Key MCP Servers for Insurance Operations

1. Salesforce MCP Server — Policy & Customer Relationship Data

Most carriers and brokers run their book of business on Salesforce Financial Services Cloud or custom Salesforce CRM instances. The Salesforce MCP server gives your AI real-time access to policyholder records, renewal pipelines, producer relationships, and claim histories.

Key capabilities for insurance:

  • Query policyholder accounts, coverage details, and premium history
  • Create and update claims records directly from FNOL intake conversations
  • Generate renewal opportunity reports and flag at-risk accounts
  • Update producer commission records and agency relationships

Insurance use case: An AI-powered renewal assistant reads the policyholder's Salesforce record, identifies upcoming expiring policies, pulls prior loss runs, and drafts personalized renewal proposals — all in a single conversation.

2. PostgreSQL MCP Server — Core Policy Administration

Many carriers run custom policy administration systems (PAS) on PostgreSQL or expose their PAS data via read replicas. The PostgreSQL MCP server lets AI query policy tables, endorsement records, and claims data directly.

Key capabilities for insurance:

  • Schema introspection to understand policy, coverage, and endorsement table structures
  • Read-only query execution for actuarial and underwriting analysis
  • Claims status lookups without logging into the PAS UI
  • Coverage verification against policy terms in real time

Insurance use case: An underwriter asks the AI to compare loss ratios across a book segment for a specific class of business. The AI queries the policy and claims tables directly, performs the calculation, and surfaces the analysis — no data extraction or spreadsheet work needed.

3. DocuSign MCP Server — Policy Execution & E-Signatures

Policy issuance, endorsements, and claims settlements all require signatures. The DocuSign MCP server enables AI to initiate, track, and complete signature workflows without leaving the AI conversation.

Key capabilities for insurance:

  • Send policy documents for e-signature directly from AI-generated workflows
  • Check envelope status and surface pending signature bottlenecks
  • Trigger automated reminders for unsigned documents
  • Download completed, signed documents to policy filing systems

Insurance use case: During a renewal conversation, the AI generates the updated policy documents, sends them for e-signature via DocuSign, and logs the issuance date in the CRM — all in one automated workflow triggered by a single prompt.

4. Filesystem MCP Server — Document Intake & Processing

Claims adjusters receive photos, police reports, medical records, repair estimates, and correspondence as files. The filesystem MCP server enables AI to read, organize, and extract data from these documents as part of structured claims workflows.

Key capabilities for insurance:

  • Read incoming claims documents (PDFs, images, text files) for content extraction
  • Organize documents into structured folder hierarchies by claim number or policy
  • Generate claims summaries from multi-document sets
  • Flag documents requiring human adjuster review

Insurance use case: An AI claims intake assistant reads an uploaded police report and damage photos, extracts key facts (incident date, parties involved, estimated damage), populates the FNOL record in the claims system, and routes the claim to the appropriate adjuster queue.

5. Gmail / Slack MCP Servers — Customer & Producer Communication

Insurance is a high-touch business. Brokers, producers, and insureds communicate via email and messaging constantly. Gmail and Slack MCP servers give AI assistants access to these communication channels for drafting, routing, and triaging.

Key capabilities for insurance:

  • Read inbound coverage inquiries and draft accurate responses using policy data
  • Triage claims status emails and route to the correct adjuster
  • Draft producer bulletins and coverage change notifications
  • Alert claims teams in Slack when new FNOLs are submitted

6. Jira MCP Server — Claims Workflow Tracking

Complex claims often involve multiple departments — adjusting, legal, subrogation, recovery. Jira (or similar project trackers) map these workflows, and the Jira MCP server lets AI query and update claims tasks across teams.

Key capabilities for insurance:

  • Check claims status across multi-department workflows
  • Create tasks for adjuster follow-ups, inspection scheduling, or legal review
  • Identify claims exceeding SLA thresholds and escalate automatically

High-Value Insurance Workflows for MCP

Automated FNOL Intake

First Notice of Loss is the first bottleneck in claims. An MCP-connected AI can intake FNOL via email, web form, or phone transcript, extract structured data, verify policy coverage via the PostgreSQL server, create the claims record in Salesforce, route the Jira task to the appropriate adjuster, and confirm receipt to the insured via Gmail — all without human data entry.

Renewal Propensity Scoring

By querying loss history, payment history, and engagement data from Salesforce and the policy database, an AI can score renewal propensity for every account in a book. Agents receive a prioritized list of accounts to contact, with draft outreach already written.

Underwriting Data Clearance

New commercial submissions often require pulling data from multiple sources — prior carrier loss runs, property databases, financial statements. An MCP-connected AI can retrieve and synthesize these data points into a structured underwriting memo, cutting clearance time from days to hours.

Compliance Audit Preparation

Regulatory exams require assembling policy records, claims files, and communication logs. The filesystem and database MCP servers let AI compile these records systematically, while DocuSign confirms signature dates and audit trail completeness.

Security Considerations for Insurance MCP Deployments

Insurance data is heavily regulated (GDPR, CCPA, NYDFS, state insurance regulations). Before deploying MCP servers in production:

  • Scope access to read-only where possible — Use read replicas for database MCP servers; restrict filesystem servers to specific claim folders.
  • Implement PII redaction — Configure AI to never include SSNs, driver's license numbers, or medical information in logs or outputs.
  • Audit logging — Every MCP tool call should be logged with user identity, timestamp, and query for regulatory compliance.
  • Role-based access — Underwriters should not have MCP access to claims adjuster data and vice versa; configure separate MCP server instances per role.

For a comprehensive guide to securing your MCP deployment, see our enterprise compliance guide and authentication patterns.

Getting Started

The fastest path for an insurance operation is usually starting with the Salesforce MCP server — it requires minimal infrastructure change and immediately surfaces the most value for producers and service teams. Add the PostgreSQL server once you've validated the workflow patterns, then layer in DocuSign and Gmail automation for end-to-end policy execution.

Browse the full MCP server directory for insurance-relevant integrations including payment processing, document management, and regulatory data providers.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

🌐

Salesforce MCP Server

The Salesforce DX MCP Server (npm package `@salesforce/mcp`) is Salesforce's official Model Context Protocol integration, built and maintained by the Salesforce CLI (salesforcecli) team to let AI assistants read, manage, and operate Salesforce orgs securely from Claude, Cursor, VS Code, Windsurf, or Cline. Rather than exposing one flat set of tools, it is organized into configurable toolsets you enable with the `--toolsets` flag: `orgs` (list and inspect the orgs you've authenticated), `data` (run SOQL queries and read/create/update records for standard and custom objects), `metadata` (deploy and retrieve source and metadata), and `users` — plus individually-gateable tools such as `run_apex_test`. This makes it useful both for developers automating deploys and Apex test runs and for RevOps teams asking Claude to "pull all open opportunities closing this quarter over $50K" or "update this deal to Negotiation." A key security design point: the server never takes raw usernames and passwords — instead it operates on orgs you have already authenticated through the Salesforce CLI (`sf org login`), which you reference by alias via the `--orgs` flag, so credentials stay in the CLI's secure store and each MCP session is scoped only to the orgs you explicitly allow. Install with `npx -y @salesforce/mcp --orgs DEFAULT_TARGET_ORG --toolsets orgs,metadata,data,users`. Apache-2.0 licensed. Community CRM-focused alternatives such as tsmztech/mcp-server-salesforce and smn2gnt/MCP-Salesforce exist for teams wanting a lighter SOQL-and-records-only server.

Local
🗄️

PostgreSQL MCP Server

The PostgreSQL MCP server is an official Model Context Protocol server maintained by Anthropic that gives AI assistants read-only access to PostgreSQL databases. By connecting Claude Desktop, Cursor, or VS Code to a running Postgres instance, developers can ask natural-language questions about their data schema, run exploratory SQL queries, inspect table structures, list available schemas, and analyze query results — all without leaving their AI chat interface. The server operates in read-only mode by design, preventing any accidental data mutations, making it safe to connect against production databases for reporting, debugging, and data exploration workflows. Core tools include executing SELECT queries, listing tables and schemas, describing column types and constraints, and inspecting indexes. Setup requires a running PostgreSQL instance and a standard connection string in postgres:// format. Install via npx using the @modelcontextprotocol/server-postgres package, passing your database URI as an argument. Teams use it to power data analysis conversations, generate schema documentation automatically, debug production data anomalies by asking Claude to inspect table contents, and build ad-hoc reports through natural-language SQL generation. Works with any PostgreSQL 12+ instance including Amazon RDS, Supabase, Neon, and self-hosted deployments.

Local
📋

DocuSign

Send, sign, and manage DocuSign envelopes and templates. Automate e-signature workflows, check document status, and retrieve signed documents programmatically.

Local
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local
💬

Gmail MCP Server

The Gmail MCP Server is the official Google Workspace Model Context Protocol integration, giving AI assistants like Claude, Cursor, and Windsurf direct access to your Gmail account. Built and maintained by the Google Workspace team, the server exposes Gmail as callable MCP tools: search the inbox with Gmail query syntax (from:, subject:, has:attachment, after:), read full email threads including message bodies and metadata, send new messages or reply-to threads, create draft emails for review, manage labels (apply, remove, list), and mark messages read or unread. This makes the Gmail MCP server essential for productivity workflows like "summarize today's unread emails from my team," "find every invoice email from Stripe last quarter," "draft a reply to this thread and label it Follow-Up," or "list all emails with attachments from this client." Authentication requires a Google Cloud project with the Gmail API enabled and OAuth 2.0 credentials configured — download credentials.json from the Google Cloud Console and follow the server's auth setup to generate an access token. Works with Claude Desktop, Cursor, VS Code, and Windsurf. With 1,200+ GitHub stars, it is the most popular official Google productivity integration in the MCP ecosystem.

Local
📋

Jira MCP Server

The Jira MCP server is Atlassian's official Remote MCP Server, giving AI assistants like Claude and Cursor direct, enterprise-grade access to Jira Software project management through natural-language interactions. Powered by Atlassian's Teamwork Graph and hosted on Cloudflare infrastructure, it requires no local process to run — authentication is handled via OAuth 2.1, making it the most secure way to connect AI to Jira in corporate environments. With this MCP server, product managers, engineers, and team leads can ask their AI to create and update Jira issues, transition ticket statuses through workflow stages, search with JQL (Jira Query Language), summarize sprint progress, view open epics and their child issues, retrieve assignee workloads, and bulk-triage backlogs. AI assistants can connect sprints to related Confluence documentation through Atlassian's graph layer, giving richer context for planning and retros. Enterprise customers including AT&T, NVIDIA, and Pfizer use Atlassian's MCP integration in production. Connect from Claude Desktop via Settings > Connectors, or add it to Claude Code with: `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp`. Cursor and Windsurf users add the remote URL to their MCP config file. No install command needed — it's a fully hosted remote MCP server.

Auth required
📁

Filesystem

Secure file operations with configurable access controls. Read, write, and manage files safely.

Local
🗄️

Airtable MCP Server

The Airtable MCP Server connects your AI assistant directly to Airtable bases, letting you read records, create entries, update fields, and query structured data using natural language — no manual spreadsheet navigation required. The leading community implementation is domdomegg/airtable-mcp-server, which exposes the full Airtable REST API as MCP tools: list all bases and tables in your workspace, fetch records from any view with optional filter formulas, create or update individual records with typed field values, and delete records by ID. Authentication uses your Airtable personal access token (or API key for legacy accounts), scoped to whichever bases you grant access. Once connected, ask Claude to "show me all leads added this week in my CRM base" or "create a new product entry in my inventory table" and the server handles the API calls. Common use cases include AI-assisted CRM workflows (pull contact records, log meeting notes back into Airtable), inventory management, content calendars, and project tracking where Airtable acts as a lightweight database. Works with Claude Desktop, Cursor, VS Code (Copilot Chat), Windsurf, and any MCP-compatible client. Install via: `npx -y airtable-mcp-server` with `AIRTABLE_TOKEN=your_token` set in your environment.

Auth required

📚 More from the Blog