Checked October 24, 2026

Claude + QQCatalyst:
what works today, and what doesn’t.

The short answer: There is no Claude connector for QQCatalyst, and Vertafore’s 2026 AI announcements do not include it. QQCatalyst does have a real REST API with OAuth, but it is for registered API partners or enterprise customers that Vertafore approves, and each agency grants access. With it, Claude can look up contacts, policies and tasks and update tasks, on demand. There are no webhooks.

Claude connector
None
Nothing official, nothing in the registries.
API access
Partner or enterprise
Registered partners, or a key plus allowlisted IPs.
Events
None found
Poll the modified-since lists.
Write-back
Yes
Partners can query, create and update.
The gate

The gate: QQ API partner or enterprise access

QQCatalyst’s API is a REST service with OAuth sign-in. Third-party apps must register with Vertafore as an API partner, and each agency then grants the app access to its data. For an agency’s own use there is enterprise API access: a key and secret from Vertafore plus a list of the IP addresses that will connect.

No price is published for either route. Vertafore’s Orange Partner Program lists QQCatalyst among the products its vetted partners integrate with.

  • The IP allowlist means the bridge should run on a server with a fixed address, not a laptop.
  • There is a developer test tenant for building before you touch real data.
What Vertafore ships

What Vertafore gives you, and what it doesn’t

QQCatalyst is actively developed (version 6.0 shipped in May 2026, with release notes updated in October), but Vertafore’s AI work this year (the Velocity AI Platform in April and the Agentic Agency release in September) names AMS360, Sagitta and other products, not QQCatalyst. None of it mentions MCP or Claude.

The API covers the core of the system:

  • Contacts: look up, insert, summaries, and lists created or modified in a date range.
  • Policies by contact, and tasks by contact or policy, with task updates.
  • Pages of 25 rows by default, and a limit of about 60 calls a minute per endpoint per agency.
  • No documented webhooks, and no Zapier or Make app.
The build

How you would actually connect Claude to QQCatalyst

With credentials, the bridge is an MCP server on a fixed-address server: it tells Claude which QQCatalyst actions exist and calls the API when asked.

  1. 01
    Ask Vertafore for API access
    Partner registration or enterprise credentials through your QQCatalyst account rep. Expect vetting and an IP allowlist.
  2. 02
    Build read tools first
    Contacts, policies and tasks. Writes (create and update tasks) come later, behind a confirmation.
  3. 03
    Handle the rate limit properly
    Going over the limit returns “unauthorized”, which looks like an expired login. The bridge must back off instead of signing in again.
  4. 04
    Mirror for book-wide questions
    Small pages and a per-minute limit make “every policy renewing in March” slow live. A nightly sync into your own store answers it fast.
  5. 05
    Host on a fixed address
    A remote server on allowlisted IPs, added to Claude as a custom connector with OAuth so each person signs in as themselves.
mcp server · qqcatalyst-bridge · tools Claude would seevia QQCatalyst API
find_contact(name | email | phone)readResolve the insured first.
get_contact_summary(id)readThe account at a glance.
list_policies(contact_id)readLines, terms, carriers.
list_tasks(contact_id | policy_id)readOpen follow-ups on the account or policy.
contacts_changed_since(date)readWhat moved since yesterday, for digests.
update_task(task_id, ...)writeClose or reassign a follow-up, after a person confirms.

Tool names are our sketch, not QQCatalyst endpoint names. Check the API help pages for the objects your access includes before building.

The limits

The limits that actually matter

  • Access is approved by Vertafore per partner and per agency, with no self-serve key and no published price.
  • Rate limiting answers “unauthorized”, not “too many requests”, which trips up naive clients.
  • No webhooks found, so nothing in QQCatalyst can wake Claude up.
  • QQCatalyst is missing from Vertafore’s 2026 AI announcements; plan as if outside AI is the only AI it will get for now.

Claude itself has one more limit on every AMS: it acts when someone asks, or on a scheduled task’s clock. It does not notice a new lead, a changed policy or a cancellation notice on its own. Anything that should happen because something changed in QQCatalyst needs a listener running outside Claude.

Where we fit

If you want QQCatalyst work that runs on its own

We are an engineering team that builds automation on top of the AMS an agency already runs. For QQCatalyst that means one of two things: we build and host the bridge above so your team can ask Claude about the book, or we skip the chat window and build the workflow itself, triggered by QQCatalyst events and checked by rules where a wrong number matters.

  • A Claude connector on your QQCatalyst data, hosted on allowlisted addresses, with a nightly mirror for book-wide questions.
  • Daily task and renewal digests per producer, built from QQCatalyst without anyone opening a chat.
  • Commercial submissions and carrier portal entry from the QQCatalyst record, with quotes written back.

The first build is live in 14 days for $2,499, charged only if your team is using it, then $2,499 a month flat. You keep the code. More on what we automate on top of QQCatalyst.

Trucking agency? Our Market Tracker connector already works in Claude today: it answers carrier questions (filings, X-dates, safety, ISS) from the federal record, so the AMS bridge only has to carry your own book.

Side by side

Three ways to put AI on QQCatalyst

Claude, no connectorClaude + a connector you buildNativeBase build
Look up a contact or policyNo: copy and paste onlyYesYes
Update tasksNoYes, with confirmationYes, with rules and confirmation
Book-wide questionsUpload an export by handSlow live; needs a mirror you buildYes, from a nightly mirror we run
React to a change in QQCatalystNoPolling onlyPolling plus your inbox
Runs with nobody askingNoOnly on a scheduled task’s clockYes: triggered by QQCatalyst changes or your inbox, on our servers
Who keeps it workingNothing to keepWhoever built itWe do, and we get the alert before you
FAQ

Claude + QQCatalyst, answered.

Does Claude work with QQCatalyst?

Not out of the box. There is no Claude connector for QQCatalyst. A custom MCP server on the QQCatalyst API can connect them once Vertafore grants access.

How do I get QQCatalyst API access?

Through Vertafore: either register an app as an API partner, which each agency then authorizes, or request enterprise API access, which comes with a key, a secret and an IP allowlist. Pricing is not published.

Is QQCatalyst being discontinued?

We found no sign of it. Version 6.0 shipped in 2026 and release notes are still being updated. It is, however, absent from Vertafore’s 2026 AI announcements.

Does QQCatalyst have webhooks?

None are documented. Integrations poll the lists of contacts created or modified in a date range.

Book a call20 minutes

Want Claude on your QQCatalyst book? We build the bridge.

Twenty minutes, no deck. You leave with a written automation map. Your first automation is live in 14 days, or you pay nothing.

First automation in 14 days · $2,499 once, only if it is live · then $2,499 / mo flat

Not ready to talk? Start with the free tools instead →

Sources

Checked on October 24, 2026 against the vendor’s own documentation first, and the pages below. Access terms change, so confirm with Vertafore before you plan a build. Where the sources are silent, this page says so rather than guessing.

Claude with other AMS