claimOS connector
Your claims, inside the AI tools you already use.
Public adjusters spend most of their day in claim files. Many also spend part of it in Claude Desktop, ChatGPT, or Cursor. The claimOS connector closes the gap: ask the assistant a question about a real claim, and the assistant has the file in front of it. No copy-paste, no screenshots, no leaving the tool.
What the connector does.
claimOS is the operating system for the public adjusting firm: claims, evidence, communications, weather reports, estimate variance, the carrier package. The connector is a thin layer over that data, exposed to AI assistants through the open Model Context Protocol (MCP) and authorized through standard OAuth 2.0.
When you connect Claude Desktop or ChatGPT to claimOS, you grant the assistant scoped access to your workspace, the same workspace you already log into at app.claimos.net. The assistant can search your claims, read a snapshot of any one of them, walk a timeline, pull policy excerpts, summarize communications, and (if you grant write scope) log tasks and timeline notes back to the file. It cannot see anyone else's claims, and it cannot send anything on your behalf.
Who it's for.
Active claimOS subscribers, working real claim files, who already use an AI assistant for some part of their day. The most common profile is a public adjusting firm, but the same connector serves appraisers, mitigation companies, roofers, and insurance attorneys with a claimOS workspace. If you do not have a claimOS subscription, the connector has nothing to talk to; start a trial first.
Each user authorizes the connector independently with their own login. A paralegal, intake coordinator, or junior adjuster gets their own credentials with scopes tuned to their role. Revoking a teammate's access is one click on Connected Apps.
Example questions.
These are real prompts the connector answers, grounded in the live claim file.
User asks the assistant
Which claims have deadlines this week?
User asks the assistant
Summarize the carrier's last three emails on the Reyes claim.
User asks the assistant
Draft a follow-up letter for stalled negotiations on the Patel file.
User asks the assistant
What's blocking us from sending the carrier package on the Wong claim?
User asks the assistant
Compare the carrier estimate to the contractor estimate on the Reyes claim.
User asks the assistant
What changed across all my claims since yesterday?
The assistant decides which tools to call based on the question. For most reads it pulls a snapshot, then drills into timeline, communications, or evidence as needed. See more concrete workflows.
Trust model.
- Per-user OAuth. Each authorization is bound to one user inside one tenant. No shared credentials, no service accounts.
- Scoped tokens. Read access (claim:read) and write access (claim:write) are separate. Issue read-only tokens by withholding write scope.
- Tokens hashed at rest. Access and refresh tokens are stored as hashes; the plaintext is shown once at issuance and never again.
- Refresh rotation. Single-use refresh tokens rotate on every exchange. A leaked refresh token works exactly once.
- RLS-scoped per tenant. Every tool query runs inside the tenant boundary already enforced by Supabase row-level security. The connector cannot widen that boundary.
- Revoke any time. The Connected Apps page in admin settings shows every authorized assistant and lets the user revoke instantly.
Full detail on the OAuth flow and scope model.
Where to go next.
- Quickstart: connect Claude Desktop or ChatGPT to claimOS in about five minutes.
- Tools reference: every tool the connector exposes, with inputs and example prompts.
- Auth and security: OAuth flow, scopes, token rotation, the Connected Apps revoke surface.
- Use cases: concrete workflows a working PA can run today.
- FAQ: common questions about pricing, staff access, data handling, and revocation.
Not yet a claimOS customer? Book a 15-minute demo or read more about the platform for public adjusters.