Connect an assistant with MCP

Discover product workflows, read scoped records and prepare reviewed work.

Integrations · Customer, Unlicensed staff, Licensed staff, Company admin, Wholesaler, Hub admin, Carrier / underwriter

How it works

Open Assistant connections in the portal help area while signed into the intended workspace. Create a read-only or preparation key.
Run the documented local stdio bridge with the portal origin and key supplied through environment variables. Never paste a key into a prompt or source repository.
For a new intake page, ask your assistant to create it with you. It reads hub_intake_setup, prepares a saved preview with hub_prepare_intake, asks for missing details, and publishes with hub_publish_intake after you approve. You can pass the saved draft link between compatible assistants.
Preparation tools require explicit consent and versions. Signing, external delivery, binding, access changes and other consequential actions return portal handoffs.
Revoke the key when finished. Delegation also ends when the original session expires, is revoked or no longer meets MFA/access requirements.

The supplied connector is a local stdio MCP bridge over the authenticated Hub RPC endpoint. It is not a hosted OAuth app-directory integration.

MCP access does not add permissions, turn on provider integrations or make unverified insurance judgments.