The USB-C Port for Healthcare AI: Why MCP Is the Protocol That Actually Matters Right Now
Table of Contents
What MCP Actually Is (and Why Everyone Keeps Explaining It Badly)
The Healthcare Interoperability Problem MCP Was Born to Solve
Athena’s Big Bet: First Mover in the EHR Space
The Real Risk Surface: HIPAA, PHI, and the Confused Deputy
Where MCP Belongs in Healthcare (and Where It Doesn’t)
Investment Thesis: What This Means for Founders and Angels
Abstract
- MCP, open-sourced by Anthropic in late 2024 and donated to the Linux Foundation in Dec 2025, solves the classic M x N integration problem for AI agents connecting to enterprise systems
- Athenahealth announced Aug 2025 an industry-first MCP server on athenaOne APIs, framing it as the connective tissue for their AI-native platform serving 160,000+ providers
- The protocol dramatically lowers the cost of building agentic health tech, but introduces serious HIPAA/PHI risk surface that founders and investors cannot ignore
- FHIR + MCP is the architectural stack that will define the next generation of clinical workflow tools
- Investment implications span ambient documentation, prior auth automation, clinical decision support, and interop infrastructure
What MCP Actually Is (and Why Everyone Keeps Explaining It Badly)
There’s a particular flavor of tech explanation that shows up in healthcare conferences where someone puts up a slide with a bunch of boxes and arrows and calls it “interoperability.” MCP has started getting that treatment. So let’s skip the slide deck version.
MCP, or Model Context Protocol, was originally released by Anthropic in late 2024 as an open standard, and then donated to the Linux Foundation’s Agentic AI Foundation in December 2025. The spec has since attracted formal backing from OpenAI, Google DeepMind, Microsoft, and AWS, which is about as close as you get to a consensus standard in AI infrastructure. As of mid-2025, there were reportedly over 5,000 active MCP servers listed in the Glama MCP Server Directory, with more than 115 production-grade vendor implementations.
The core problem MCP solves is what computer scientists call the M x N integration problem. If you have five AI models and five enterprise systems, you don’t have ten integrations, you have twenty-five. Each model needs custom glue code for each system. Every time the model updates or the API version changes, something breaks. Multiply that across a health system’s tech stack, which might include a primary EHR, a PACS system, a lab information system, a scheduling platform, and several revenue cycle tools, and the engineering cost of connecting AI agents to real clinical data is enormous. MCP flattens that matrix. Instead of point-to-point custom integrations, every model plugs into MCP and every system plugs into MCP. The analogy that has stuck, because it’s genuinely accurate, is USB-C. One port, multiple devices, standardized handshake.
Technically, MCP operates over a lightweight JSON-RPC layer and defines three core building blocks for how AI agents interact with external systems: action tools (things the agent can do), read-only resources (data the agent can pull), and reusable prompt templates. The agent doesn’t need to know the underlying schema of your EHR or your billing system. It expresses a need, the MCP server handles the translation, applies access controls, and returns a structured response. The host layer can be built to encrypt in transit, log every call, and enforce least-privilege access. Done right, it’s actually a more auditable architecture than a lot of the bespoke integrations currently running in production across health systems.
The reason this matters specifically in healthcare is that health data is probably the most structurally complex regulated data domain that exists. FHIR, HL7, DICOM, LOINC, SNOMED, RxNorm, ICD-10, prior auth formats, payer-specific EDI, state-level HIE feeds, the list goes on. Before MCP, connecting an LLM to even a subset of this required domain-specific engineering that only a handful of teams really got right. What MCP does is provide the standardized discovery and communication layer that makes it possible for a well-built agent to navigate that complexity without custom hardcoding. When paired with FHIR R4, which is the current gold standard for structured clinical data exchange, you start to get a stack that can actually express the full context of a patient encounter to an AI model in a controlled, auditable way.
The Healthcare Interoperability Problem MCP Was Born to Solve
