← Back to directory

Duck Creek

Duck Creek Technologies · Insurance & Annuities

MCP ServerVendor

MCP support within Duck Creek's insurance-native Agentic AI Platform. Its AI Gateway layer provides a marketplace, registry and standardised protocols (MCP and A2A) so Duck Creek, partner and carrier-built agents can reach core policy, claims, billing and risk data, alongside new agentic underwriting and FNOL applications. Caveats: MCP here is one protocol inside a broader agentic platform, not a standalone published MCP server — treat this listing as protocol support rather than a discrete server. Duck Creek core customers only. The FNOL application was built with Google Cloud on Gemini models. Connection details are not publicly published.

P&C insuranceunderwritingclaimsagentic platform
Status
Vendor
Auth
Enterprise
Hosting
Remote
Community rating
Not rated yet
Role
Gateway

Reaches many systems at once. One connection that fans out to hundreds of apps, trading depth for breadth. All seven roles →

Open documentation →
Rate this server

How to connect Duck Creek

Step 1

Check the vendor's documentation

This listing does not publish a public endpoint or install command yet. Open the vendor documentation above for access details, then follow the general steps in our connection guide.

Step 2

Authenticate with Enterprise

Access is provisioned by the vendor or your firm's administrator. Ask your account team for MCP access, sandbox credentials and the allowed data scopes.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Insurance & Annuities.

Planning data-gathering gap check

What's still missing before a plan can be built.

Financial PlanningFinancial PlanningInsurance & Annuities

Read-only: compare the planning inputs on file for <client name> in the planning tool against what the insurance and annuity records actually show, and list what is missing, stale or inconsistent before I build or update a plan: income, expenses, balances, coverage amounts, riders, premiums, beneficiaries, goals and assumptions. Output Item / Value in plan / Value at source / Status / Last updated. Do not edit the plan or write any assumption — flag gaps and mismatches rather than filling them in.

Guardrail · Read-only. Never let a tool invent a planning assumption.

Insurance and protection gap review

Coverage on file versus what the plan implies.

Financial PlanningInsurance & AnnuitiesFinancial Planning

Read-only: list <client name>'s in-force coverage — life, disability, LTC, annuity riders — with carrier, benefit, term and cost, then compare against the protection need implied by the plan. Flag gaps and expiring coverage. No product recommendations and no applications. Note where policy data could not be verified.

Guardrail · Read-only. Product recommendations require suitability review, not a chat tool.

In-force policy summary

Every policy on one page, with the details that matter.

Insurance & Annuity ReviewInsurance & Annuities

Read-only: build one in-force summary for <client name> by combining every connected insurance source — carrier or policy-administration data and any independent policy-review or annuity-data tool. Show carrier, type, face amount or benefit, premium, term or maturity, ownership, beneficiaries and the source tool for each line, and flag any field where two sources disagree or one source has no record of a policy. Mask policy numbers to the last four characters. Do not change beneficiaries, request changes, or submit anything to a carrier.

Guardrail · Read-only. Beneficiary and ownership changes are never done from a chat tool.

Read the full connection guide →