The integration layer healthcare always needed.

The Model Context Protocol (MCP) is the open standard Cline uses to connect AI agents like DrClaw to outside services. Building a new Integration on MCP takes days instead of quarters, the connection is consistent across every Connector you activate, and partners listing through the upcoming Marketplace can ship their Connector against the same protocol Cline uses internally. For your practice, MCP means new Connectors arrive faster and break less.

Skills are abilities you give DrClaw so he knows how to do specific kinds of work, like running a prior authorization or following up after a visit. Connectors are the integration layer that connects DrClaw to outside systems like your EHR, your payment processor, or your labs vendor. Skills tell DrClaw what to do. Connectors tell him where to do it.

No. That's the point. Cline Connectors are pre-built so you don't have to wire anything yourself. Cline Native Connectors activate with a click. Cline-managed Integrations enable with an API key or OAuth, and the monthly fee is added to your Cline invoice. The integration logic, the error handling, and the endpoint maintenance are all handled on Cline's side, the same way Keragon runs HIPAA workflow automation.

When a vendor changes their API, updates their auth scheme, or modifies their rate limits, Cline's engineering team updates the Connector on your behalf. You don't get paged. You don't have to fix anything. The Connector's uptime SLA covers vendor-side disruptions inside the platform's reasonable control, with retry logic, error queuing, and incident notifications built in.

Every Connector ships under your signed Cline BAA, with encryption in transit and at rest and per 45 C.F.R. § 164.312(b) audit logging on every transaction. Connectors that integrate with third-party services only activate once the vendor's own BAA covers your account, so the chain of compliance is intact end to end.

A Cline-managed Integration is one that Cline integrates and maintains on your behalf, like Ease for payments or Twilio for SMS. You pay a monthly fee for the integration, the same way Keragon prices workflow automation, and Cline handles auth, uptime, BAA, and API changes. A Marketplace Connector is partner-built, where the vendor integrates against Cline's API and MCP documentation, lists their Connector in the Cline Connector Marketplace, and Cline takes a 15% fee on subscription revenue. The Marketplace is shipping later this year.

Yes. Practice and Scale plans include custom Connector requests, with Practice covering one per quarter and Scale covering unlimited. Enterprise plans include custom Connectors built on demand. If the vendor has a public API and a willingness to sign a BAA, Cline can typically build the Connector within a few weeks.

The 15% fee applies only to Type 03 Marketplace Connectors, the partner-built ones sold through the Cline Connector Marketplace. It covers payment processing, BAA distribution, customer billing, refund handling, marketplace placement, and the platform infrastructure. Cline Native and Cline-managed Integrations are not Marketplace Connectors, so the fee does not apply to them. There's no listing fee, no upfront cost, and partners earn 85% of subscription revenue net of the marketplace fee.

No. API call limits reset at the start of each billing period. If you exceed the included volume on any Connector, Cline emails you before the cap is reached and offers either a top-up at a per-call rate or an upgrade to a higher plan. Workflows keep running while the cap is being handled.

Yes. Connectors can be deactivated or cancelled inside your Connectors dashboard at any time. Cline Native Connectors deactivate immediately. Cline-managed Integrations cancel at the end of the current billing period since they're prepaid for that month. The Connector stays available in the directory if you want to resume later.