Guidewire Connections 2026 Recap: Agentic Insurance, AI Connect & MCP Servers Take Center Stage
Fresh back from Las Vegas! Here is what every Guidewire developer, architect, and BA needs to know about Guidewire’s new Agentic Insurance framework, native Model Context Protocol (MCP) servers, and AI coding assistants for Gosu and Jutro.
If you walked the halls of Guidewire Connections 2026 in Las Vegas this October, one theme was impossible to miss: the P&C industry has officially moved past isolated "chat-with-your-PDF" AI pilots and into Agentic Insurance embedded directly inside the core platform.
Whether you build on PolicyCenter, ClaimCenter, or BillingCenter, the announcements from the keynote and developer breakout sessions mark the biggest architectural leap since the launch of Guidewire Cloud Platform (GWCP). Let’s break down what actually shipped and what it means for our day-to-day engineering work.
1. What "Agentic Insurance" Actually Means for Core Systems
For the last two years, insurers experimented with generative AI on the edges—summarizing a claim note here, extracting a broker ACORD form there. At Connections 2026, Guidewire introduced a unified, governed Agentic Framework built right into GWCP.
Instead of treating AI models as external black boxes, autonomous agents can now operate within strict InsuranceSuite guardrails:
- Claims Triage & Subrogation Agents: Automatically cross-reference First Notice of Loss (FNOL) intake with policy coverages, police reports, and telematics feeds, then queue up reserve recommendations for the adjuster.
- Commercial Underwriting Co-Pilots: Ingest multi-schedule broker submissions, flag appetite mismatches against HazardHub geospatial scores, and pre-populate PolicyCenter quotes.
- Human-in-the-Loop Governance: Every agent action is versioned, auditable, and bound by the same role-based permissions and authority limits as human users.
"The magic isn't just calling an LLM—it's giving an agent safe, transactional context inside PolicyCenter and ClaimCenter without breaking compliance."
2. AI Connect & Native Model Context Protocol (MCP) Servers
For the engineering crowd, the most exciting reveal was AI Connect and first-class support for Model Context Protocol (MCP) servers across the Cloud API surface.
Rather than writing brittle glue code for every LLM provider, Guidewire's model-agnostic layer exposes standardized MCP tools on top of InsuranceSuite REST endpoints and App Events:
{
"mcpServer": "gwcp-claims-context",
"tools": [
"getClaimExposureSummary",
"evaluateSubrogationPotential",
"draftAdjusterActionPlan"
],
"governancePolicy": "require-adjuster-approval-above-5000"
}
Because it is model-agnostic, carriers like Länsförsäkringar, Gore Mutual, and WSIB can plug in their preferred foundation models hosted on AWS Bedrock, Azure OpenAI, or Vertex AI while keeping policyholder PII inside their own tenant boundary.
3. Developer Assistants for Gosu and Jutro
Let's be honest—general-purpose coding assistants have historically struggled with Gosu enhancements, PCF nuances, and Jutro metadata configurations because most training data lives inside private enterprise repos.
Guidewire showcased domain-trained developer assistants that understand:
- Cloud Assurance rules and forbidden internal APIs.
- Upgrading legacy on-prem Gosu classes into clean Cloud Integration Gateway services.
- Scaffolding Jutro Digital Platform micro-frontends from Advanced Product Designer (APD) schemas.
If you haven't explored the new developer preview in Guidewire Education yet, now is the time—especially before the next ski-release certification wave opens!
Francesco
Contributor to GWDEVS — Unofficial Guidewire Community, News Site and Job Board.

