Connect in about five minutes.

Three steps.

1. Generate OAuth credentials in claimOS

   Sign in at app.claimos.net and open Admin → Settings → Connected Apps. Click “Create new connection,” give the assistant a recognizable name (e.g. “Claude Desktop, Andy's laptop”), and pick the scopes you want to grant.

   Most users start with claim:read only. Add claim:write when you want the assistant to log tasks and timeline notes. Add offline_access if you want the assistant to keep working without re-authorizing every hour.

   claimOS shows the client ID, client secret, and authorization URL exactly once. Copy them somewhere safe; the secret cannot be retrieved later. If you lose it, generate a new credential and revoke the old one.

   Screenshot: Connected Apps → Create new connection

2. Add claimOS in your assistant

   The exact menu names vary slightly between assistants, but the flow is the same: open the connector settings, add a new connector, paste the URL and credentials, and click Authorize.

   Claude Desktop

   1. Open Settings → Connectors.
   2. Click “Add custom connector.”
   3. Paste the authorization URL from claimOS. Claude Desktop reads the OAuth metadata automatically.
   4. Sign in with your claimOS account on the consent screen and click Allow.

   ChatGPT

   1. Open Settings → Apps & Connectors → Custom (Team, Business, Enterprise, or Education plans).
   2. Add the claimOS connector by URL.
   3. Authorize on the consent screen.

   Cursor and other MCP clients

   Any client that speaks MCP over HTTP and supports OAuth Bearer tokens works. Add the claimOS endpoint as an MCP server, paste the OAuth credentials, and the client handles the rest.

   Screenshot: Claude Desktop, Settings → Connectors → Add

3. Run your first query

   Ask the assistant about a real claim. The first call usually goes through search_claims to resolve the name, then get_claim_snapshot to anchor the file, then whatever tool fits the question.

   Try this

   “What's open on the Reyes claim and who owes a reply?”

   Try this

   “Show me the carrier's last estimate on the Patel file and where the contractor disagrees.”

   If the assistant returns a structured summary with citations, you're done. If you see an authorization error, jump to troubleshooting below.

Troubleshooting.

“invalid_client” or “unauthorized” on the consent screen

The credentials in your assistant don't match what claimOS has on file. Most often this is a stale client secret after rotation. Open Connected Apps in claimOS, generate a fresh credential, and re-add the connector in the assistant.

“insufficient_scope” when the assistant tries to log a task

Write tools (log_task, log_note) require the claim:write scope. Either re-issue the connection with that scope checked, or restrict the assistant to read-only operations.

The assistant says “no claim is in scope”

The connector requires claimId on every tool except search_claims. Ask the assistant to look the claim up by name first; once the assistant has resolved a claim id, it can call other tools.

Tokens expire while the assistant is working

Access tokens last one hour. Without offline_access, the assistant will ask you to re-authorize when an access token expires. Add that scope on the next credential issuance to skip re-auth.

Subscription lapsed

Tokens stop working immediately when a claimOS subscription ends. Re-add the connector after re-subscribing; nothing about your data needs to be re-imported.

Still stuck? Email hello@claimos.net with the assistant name and the error text.