Google Drives MCP for Insurance Agents

Document access and retrieval from Google Drive for policy packets, forms, and proposal attachments. Securely connect your AI agents (Claude, ChatGPT, Codex, Hermes, OpenClaw) with Google Drives via MCP to automate insurance workflows.

Connect Get a Demo ↗

Works with OpenAI Claude Codex Hermes OpenClaw

Supported Tools 3

gdrive.file.list

Exposes the gdrive.file.list capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Google) authorization.

gdrive.file.read

Exposes the gdrive.file.read capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Google) authorization.

gdrive.file.search

Exposes the gdrive.file.search capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Google) authorization.

Connect Google Drives via MCP

Add Google Drives to your MCP config. Auth: OAuth 2.0 (Google) · Transport: HTTPS (JSON-RPC)

MCP Definition JSON

{
    "id": "google-drive",
    "name": "Google Drives",
    "version": "1.0.0",
    "transport": "https",
    "auth": {
        "type": "oauth2_google"
    },
    "capabilities": {
        "tools": [
            "gdrive.file.list",
            "gdrive.file.read",
            "gdrive.file.search"
        ],
        "resources": [
            "gdrive://file/{id}"
        ],
        "prompts": [
            "document.coverage.extract"
        ]
    }
}

Prudens Path Recommended

Use Google Drive connector in MCP Insurance Connect so Prudens automations can ingest and act on document context safely.

Non-Prudens Alternative

If Prudens is unavailable, connect Google Drive through native OAuth and route files through your own retrieval + MCP tool layer.

Why use Google Drives?

Insurance-Native Integration

Google Drives is connected via MCP Insurance Connect — purpose-built for insurance agency workflows, not generic tools.

Managed Auth

Authentication via OAuth 2.0 (Google) is handled centrally. No hard-coded credentials, no token management in your agent code.

Agent-Optimized Tools

All 3 tools are structured for LLM consumption — clean schemas, reliable execution, full audit trail for every agent action.

Prudens + Fallback Paths

Every app includes a Prudens-native implementation and a standalone fallback so your agent stack stays portable and resilient.