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

The gate: an Epic SDK or API license from Applied

Epic has two programmatic doors. The Epic SDK is the long-standing one: SOAP and REST services licensed per agency, renewed every year, with the license status shown on the agency’s server. The newer Applied Epic APIs are REST, and Applied’s own description says they need an SDK-API license, a utility purchase and Epic itself, with an API key and scopes.

Neither price is published. Integrators report getting credentials through the agency’s Applied account manager, with sandbox work before production and Applied approval for go-live.

• The agency, not the developer, holds the license, so this starts with your Applied account manager.
• Applied’s docs and samples lean .NET; budget for that if your developer does not.
• Applied’s new Vendor Certification Program covers named vendors (Sonant, Quandri, Xilo and others). A one-off Claude bridge you build is not one of them.

What Applied gives you, and what it doesn’t

Applied’s AI bet is native. Epic Conductor, announced at Applied Net in September 2026, adds natural-language search, document extraction, quote comparison and remarketing inside Epic. The announcement does not mention MCP, outside models such as Claude, or developer access, and gives no general-availability date or price.

Around the edges, Epic already has pieces a Claude setup can lean on:

• REST APIs Applied names for clients, contacts and attachments, plus benefits and bond utilities. Integrators also report policy and activity APIs.
• The Outlook add-in’s “Attach to Epic”, so an email Claude drafted can be filed by the person who sends it.
• Epic reporting and dashboards, which export to spreadsheets Claude can read.
• No Zapier or Make app, and no documented webhooks.

How you would actually connect Claude to Applied Epic

With a license in place, the bridge is an MCP server: a small program that tells Claude which Epic actions exist and calls the Epic API when Claude asks. Plan on weeks, most of it spent on access and testing, not code.

1. 01
   License and credentials

   The agency buys the SDK or SDK-API license and gets sandbox credentials through Applied. Production keys follow Applied’s approval.
2. 02
   Build the MCP server

   Wrap the REST APIs first and fall back to the SDK where REST does not reach. Map each Claude user to an Epic user code so changes stay attributed.
3. 03
   Choose where it runs

   Inside your network beside Claude Desktop, or as a remote custom connector. A remote one must be reachable from Anthropic’s cloud, so a firewalled Epic needs Anthropic’s addresses allowed.
4. 04
   Default to read-only

   Turn on writes one at a time, each behind a confirmation, starting with activities and attachments.

The limits that actually matter

• License cost is unpublished and renews every year.
• Integrators rate the REST APIs as narrower than the SDK, so some work still means SOAP.
• No webhooks found: nothing in Epic can wake Claude up.
• A remote connector needs Epic data reachable from the internet; many agencies will prefer a local setup.
• Epic Conductor will do some of the same jobs natively; check its roadmap before you build a duplicate.

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 Applied Epic needs a listener running outside Claude.

If you want Applied Epic work that runs on its own

We are an engineering team that builds automation on top of the AMS an agency already runs. For Applied Epic 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 Applied Epic events and checked by rules where a wrong number matters.

• A Claude connector on your Epic license, hosted and permissioned per user, read-first.
• Scheduled jobs that read Epic and do the work without a chat window: renewal packets, missing-document chases, activity clean-up.
• Carrier portal entry from the Epic account, with quotes and documents attached back, where the API does not reach the carrier.

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 Applied Epic and our Applied Epic integration engineering.

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.

Claude + Applied Epic, answered.