Can I see the latest notes added to a specific claim?

Yes! Use the `list_claim_notes` tool with the unique claim ID. The agent will return all internal notes associated with that claim, allowing you to catch up on recent updates.

How do I check the list of pending activities for the whole team?

Use the `list_claim_activities` tool. Your agent will fetch all current tasks and activities across all claims, giving you a high-level view of the team's workload.

Where do I find my ClaimCenter Cloud API credentials?

These credentials are provided by your Guidewire administrator. You will need a username and password with 'Cloud API' permissions, along with your organization's specific instance URL.

Guidewire ClaimCenter MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: Guidewire ClaimCenter
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Guidewire ClaimCenter and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "guidewire-claimcenter": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Guidewire ClaimCenter MCP Server

Connect your Guidewire ClaimCenter account to any AI agent and take full control of your insurance claims management through natural conversation. Streamline how you monitor and update claims natively.

GitHub Copilot Agent mode brings Guidewire ClaimCenter data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Claim Oversight — List and retrieve details for all active and historical insurance claims natively
Exposure Intelligence — Access and monitor exposures associated with specific claims flawlessly
Activity Management — List and review current activities and tasks across all claims securely
Document & Note Auditing — List internal notes and uploaded documents for any claim flawlessly
User & Contact Logistics — Access internal user rosters and shared contacts, including claimants and vendors, securely
Workflow Visibility — Retrieve detailed claim metadata, policy numbers, and status updates directly within your workspace

The Guidewire ClaimCenter MCP Server exposes 8 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Guidewire ClaimCenter to VS Code Copilot via MCP

Follow these steps to integrate the Guidewire ClaimCenter MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Guidewire ClaimCenter

Ask Copilot: "Using Guidewire ClaimCenter, help me...". 8 tools available

Why Use VS Code Copilot with the Guidewire ClaimCenter MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Guidewire ClaimCenter through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Guidewire ClaimCenter + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Guidewire ClaimCenter MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Guidewire ClaimCenter MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect Guidewire ClaimCenter to VS Code Copilot via MCP:

get_claim_details

Get detailed information for a specific claim

list_claim_activities

List current activities and tasks across all claims

list_claim_contacts

List shared contacts (claimants, vendors, providers)

list_claim_documents

List uploaded documents for a specific claim

list_claim_exposures

List exposures associated with a specific claim

list_claim_notes

List internal notes for a specific claim

list_claimcenter_claims

List insurance claims from Guidewire ClaimCenter

list_claimcenter_users

List internal users and claim adjusters

Example Prompts for Guidewire ClaimCenter in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Guidewire ClaimCenter immediately.

"List all claims with a status of 'Open' in ClaimCenter."

"Show me the exposures for claim '000-01-0001'."

"Who is the primary contact for claim '000-01-0002'?"

Troubleshooting Guidewire ClaimCenter MCP Server with VS Code Copilot

Common issues when connecting Guidewire ClaimCenter to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Guidewire ClaimCenter + VS Code Copilot FAQ

Common questions about integrating Guidewire ClaimCenter MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.