Install
/plugin install healthcare@healthcareWho it's for
For people doing payer, provider, pharma, or general engineering work who want one plugin that brings both skills and already-connected hosted MCP. The official repository is https://github.com/anthropics/healthcare It states One plugin for healthcare work, and Skills only load when relevant, so the bundle stays cheap. It is not a tool that pours every healthcare capability into every session. The materials do not name applicable regions, compliance certifications, or a required agent product.
Better first tasks are reversible and checkable: extract structured fields with provenance from clinical notes, or answer questions over a contract corpus with citations. Do not drop real patient identities into the first try; the materials also give no de-identification or authorization steps.
First try in 3 minutes
The official install path is two commands in sequence: add the marketplace first, then install healthcare@healthcare:
/plugin marketplace add anthropics/healthcare
/plugin install healthcare@healthcare
Preconditions: the current agent UI can run the /plugin commands above, and you intend to write the plugin into this workspace. The materials do not name a runtime version, secrets, or other installers. Side effect: the workspace will install the healthcare plugin and reference hosted MCP. After running, confirm the plugin name is healthcare@healthcare before any skill call. Do not install the v1 per-skill aliases.
Low-risk task: open .mcp.json in the plugin, confirm the hosted service is Hosted, no setup, and that it is only referenced — you do not need to stand up a local copy. Do not connect a real medical-record system at this step, and do not upload original contracts. If you must try a skill, trigger clinical-note-extract with short synthetic text only, and check that span-level provenance and null-safety appear; do not treat the output as a clinical conclusion.
Success signal: the plugin shows as healthcare@healthcare, .mcp.json shows the hosted reference, and only relevant skills are loaded. If the UI asks for a secret that does not appear in the materials, or wants to install alias plugins together, stop immediately.
Use cases
Case 1: Extract structured data from clinical notes. Maps to clinical-note-extract: Extract structured data from clinical notes with span-level provenance and null-safety. For people who already have a synthetic note and need span-level provenance from the source text. The materials do not specify input format or field list; what you can confirm is that results should carry provenance and keep null-safety when data is missing. Do not use unauthorized medical records for the first check.
Case 2: Answer questions over a contract corpus with verified citations. Maps to contracts: Answer a question across a corpus of contract documents with verified citations. For people who want to aim a question at multiple contracts and need citations that can be checked. The materials do not say how to import the corpus or which file types; all you can confirm is cross-document questions plus verified citations. Do not write this as automatic contract editing or automatic signing.
Usage limits
v1 per-skill and per-server plugins can still be installed, but they are only deprecated aliases and all resolve into the single healthcare plugin. Official guidance: Switch to healthcare@healthcare, and it states aliases will be removed in a future release. New projects should not keep depending on the old entry points prior-auth-review, fhir-developer, cms-coverage, icd10-codes, npi-registry, pubmed.
Hosted MCP is described as needing no local setup, but the materials do not list server names, quotas, or a data-retention policy. clinical-trial-protocol can Generate clinical trial protocols for medical devices or drugs — that generates a draft, not a completed filing. Skills load on demand; there is no guarantee a given skill appears in an unrelated conversation. The materials have no other install commands.