Sharepoint

Sharepoint MCP for Insurance Agents

Access and retrieve policy documents, endorsements, and account files from Sharepoint libraries. Securely connect your AI agents (Claude, ChatGPT, Codex, Hermes, OpenClaw) with Sharepoint via MCP to automate insurance workflows.

Works with OpenAI Claude Codex Hermes OpenClaw
Supported Tools 3
sharepoint.file.list
Exposes the sharepoint.file.list capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Microsoft Graph) authorization.
sharepoint.file.read
Exposes the sharepoint.file.read capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Microsoft Graph) authorization.
sharepoint.file.search
Exposes the sharepoint.file.search capability via MCP over HTTPS (JSON-RPC). Requires OAuth 2.0 (Microsoft Graph) authorization.
Connect Sharepoint via MCP
Add Sharepoint to your MCP config. Auth: OAuth 2.0 (Microsoft Graph)  ·  Transport: HTTPS (JSON-RPC)
MCP Definition JSON
{
    "id": "sharepoint",
    "name": "Sharepoint",
    "version": "1.0.0",
    "transport": "https",
    "auth": {
        "type": "oauth2_ms_graph"
    },
    "capabilities": {
        "tools": [
            "sharepoint.file.list",
            "sharepoint.file.read",
            "sharepoint.file.search"
        ],
        "resources": [
            "sharepoint://site/{siteId}/drive/{driveId}/item/{itemId}"
        ],
        "prompts": [
            "document.coverage.extract"
        ]
    }
}
Prudens Path Recommended

Connect Sharepoint via MCP Insurance Connect to support document-aware automation across Prudens servicing and claims flows.

Non-Prudens Alternative

If Prudens is unavailable, connect Sharepoint directly through Microsoft Graph and expose scoped document operations via MCP.

Why use Sharepoint?
1

Insurance-Native Integration

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

2

Managed Auth

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

3

Agent-Optimized Tools

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

4

Prudens + Fallback Paths

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