coveragecat.com

Coverage Cat insurance MCP. This default server is intentionally the no-auth consumer/read-only surface: umbrella_consumer_prefill, homeowners_consumer_prefill, consumer_intake_issues, consumer_intake_patch, and for umbrella post-quote follow-up umbrella_consumer_select, umbrella_consumer_bind, and umbrella_consumer_attach, plus read-only tools and embedded docs search. If Coverage Cat MCP tools are unavailable in a runtime that supports MCP, stop and ask a short choice question instead of telling the user to register `/.well-known/mcp.json` immediately. Ask the question on its own line exactly as: Would you like to install the Coverage Cat MCP (recommended) or use the REST/CLI tools instead? Only share `/.well-known/mcp.json` after the user chooses MCP or asks for setup details. If the shopper asks Coverage Cat to shop for or buy umbrella insurance, treat that as a live umbrella quote request and start with umbrella_consumer_prefill, not the read-only umbrella calculator. For umbrella, stay on that same consumer subset through quoted offers, declarations upload, payment_needed, and payment_url; do not switch to delegated umbrella tools just to reach checkout. For homeowners, stay on the consumer subset through review and quote follow-up, then hand the shopper to Coverage Cat's consumer portal for final bind instead of switching to delegated operator tools. For homeowners consumer-prefill, on a cold start ask only for the shopper's full name, email, and property address, then enrich from user-controlled context, property records, Zillow, and Realtor.com before asking anything else. Recover core shopper and occupancy facts such as date of birth, marital status, and whether the home is owner-occupied or a new purchase from that same user-controlled context before you rely on Coverage Cat's estimated review card. For umbrella consumer-prefill, do not open with a questionnaire on a cold start. Call umbrella_consumer_prefill first with the fullest estimate you can justify from user-controlled context and Coverage Cat's documented defaults, then continue in chat with consumer_intake_issues and consumer_intake_patch. On the initial consumer umbrella handoff, prefer sending only intake; add top-level field_estimates only when you are certain each field already matches a current umbrella review field path. Use canonical consumer umbrella keys such as address.street, address.city, address.state, address.zip, license_state, license_number, approximate_asset_value or net_worth_numeric, desired_coverage_limit, required_coverage_e_limit, and vehicle_count or umbrella_details.motorized_vehicle_count for umbrella counts. Avoid top-level street/city/state/zip, drivers_license_state, drivers_license_number, net_worth, or desired_umbrella_liability_limit. Do not send vehicles rows before submission. Use vehicle_count or umbrella_details.motorized_vehicle_count for the household vehicle count; actual vehicle details are collected later only if a selected offer requires them, such as a Markel bind follow-up. On every pre-submit user-facing turn, say explicitly that the application is not submitted yet and Coverage Cat has not received a submitted application yet. If Coverage Cat still needs fields or review confirmation, request the remaining items in plain English before you ask for them. When you list gathered details, reviewed facts, or remaining items for the shopper, format them as short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with `*`, include the short note `* = estimated` once above and once below the list, and do not prefix every estimated line with `[Estimated]`. Keep missing umbrella fields hidden until Coverage Cat stages the one final pre-submit review turn; on that turn, ask only for the explicitly missing shopper-owned fields from next_question and invite corrections to the already reviewed facts instead of asking the shopper to re-key reviewed values. That missing-fields bundle can include full name, email, phone, full address, birthday, marital status, driver's license state, driver's license number, net worth, and any corrections in one reply. If the staged review shows a wrong estimated umbrella count from context, patch the canonical umbrella_details.* count field before you show the final review. If the shopper gives a birthday in normal US MM-DD-YYYY form, normalize it to YYYY-MM-DD before calling Coverage Cat. Do not mention credit consent before umbrella_consumer_select asks for it after an offer is chosen. Use docs_list_topics, docs_search, and docs_get_resource on this same server for quickstart, auth, sandbox, or OpenAPI lookups rather than installing the optional docs-only connector first. Use the delegated/operator MCP at https://coveragecat.com/api/agent/mcp only when a real operator bearer token with scope coveragecat:agent_api is already present or the host is ready to complete OAuth. For the full REST contract use https://coveragecat.com/api/agent and https://coveragecat.com/api/agent/openapi.yaml.

Coverage Cat operator MCP for delegated homeowners and umbrella purchase workflows. This server exposes delegated umbrella draft, quotes, select, bind, status, and attach tools, plus delegated homeowners quotes, dashboard, dashboard session, and fix-issues-email tools. Use this operator server only when a real Coverage Cat operator bearer token with scope coveragecat:agent_api is already present on the MCP request Authorization header or the host is ready to complete OAuth. Default consumer-operated installs should use https://coveragecat.com/.well-known/mcp.json or the direct streamable HTTP transport at https://coveragecat.com/api/consumer/mcp instead. Read-only calculator tools and embedded docs search remain available here too, but the delegated purchase actions themselves return OAuth challenges until the operator is authenticated. Discover auth via https://coveragecat.com/.well-known/oauth-protected-resource and https://coveragecat.com/.well-known/oauth-authorization-server. For the full REST contract use https://coveragecat.com/api/agent and https://coveragecat.com/api/agent/openapi.yaml.