VECTORCARE MCP SERVER
VectorCare MCP: one connection for every agent that books patient transport
AI agents in EHRs, care coordination products and care apps will need a way to book patient transport. We are designing the VectorCare MCP server so that each agent connects to VectorCare once. VectorCare then connects the request to the transport network.
Talk to usRead about VectorCare and Epic Connectors
This page describes our design and direction. It is not a product release.
Every agent needs a path to the network
Hospitals will run many AI agents. Each agent can ask for a ride. But an agent cannot find a credentialed provider, a contracted rate or a vehicle that shows up. A separate link from each agent to each dispatch system does not scale.
Agents can be built by anyone. The network cannot.
Agent to agent, not EHR to EHR
VectorCare is the hub between agents. In our design, an EHR agent asks for a ride. VectorCare finds the options and books the trip. A CAD (computer aided dispatch system) runs the trip. The flow is EHR agent to VectorCare to CAD.
It is not EHR to EHR, and it is not only for EHRs. A care coordination product or a care app can connect the same way. People use the same hub through our SMART on FHIR app and the VectorCare web app.
For a CAD team, our design means one connection to VectorCare. Requests from many agents then reach your dispatchers in one format, with the trip details they need.
Under the hub is the VectorCare network: credentialed providers, contracts and rates, service levels, dispatch and tracking, and trip history. VectorCare is the software rails. It is not a broker.
How it is built: the open API comes first
The VectorCare open API is the foundation. Our goal is to put every major product function in the API, so VectorCare can work end to end with no screen.
For agents: the MCP server. The MCP server is a thin wrapper over the open API spec. Each function in the API can become a tool for agents.
For people: the SMART on FHIR app and web app. These also wrap the same API.
Why thin layers. If the agent standard changes, we add a new adapter on the same API. We do not rebuild the product.
Ways in to VectorCare
For agents
MCP server
For agents in EHRs, care coordination products and care apps. The agent calls VectorCare tools through the Model Context Protocol. We are designing this now.
For people
SMART on FHIR app
For clinicians and case managers who order transport from the EHR. It runs on SoFaaS, our SMART on FHIR service.
About our SMART on FHIR appRoadmap
Epic Connectors
Epic announced Connectors on October 21, 2026, built first on MCP. We are designing the VectorCare MCP server so that it can become an Epic Connector.
VectorCare and Epic ConnectorsNext
CDS Hooks
The next step for SoFaaS. The EHR calls VectorCare when a clinician acts, and VectorCare returns a card.
How CDS Hooks fitsWhat an agent could do
These examples show the design. They are not a list of product features. In each one, the agent reads first. A person confirms before anything is booked or changed.
"Find transport options for the patient in bed 12. Discharge is Friday at 2 PM."
The agent shows the options. It does not book.
"Check that coverage is on file for a wheelchair van for this patient."
Read only. If the record does not say, the agent tells you. It does not guess.
"Book the 10 AM stretcher ride from that list."
The agent shows the full request. A person confirms before VectorCare sends it to the provider.
"Where is the ride for the patient in room 4B?"
Read only. The status comes from the trip record in VectorCare.
"Cancel tomorrow's dialysis ride for this patient."
A person confirms. The provider gets the cancellation through VectorCare.
"The discharge moved to Saturday. Move the ride."
The agent asks before it changes the booking. If a detail is missing, it asks for it.
Designed for control
Scoped permissions.
We design the server so that the hospital decides what an agent can read and what it can change.
A person confirms.
We design it so that a person confirms each booking and each cancellation.
Every call logged.
We design it so that each call is recorded with the caller, the inputs and the outcome.
Narrow tools.
Each tool does one thing, so your review team can check it.
What is next: CDS Hooks for SoFaaS
CDS Hooks is an open HL7 standard. It lets the EHR call an outside service when a clinician acts in the chart.
We are designing a CDS Hooks service for SoFaaS. When a clinician signs a discharge order, the EHR calls VectorCare. VectorCare returns a card with a "Request transport" button. The aim is one click.
Sometimes the EHR does not record a detail we need, or we cannot see it. Examples are mobility needs, the payer or the pickup window. Then the card asks a short follow-up question, or it opens our SMART on FHIR app to finish the request.
Source: CDS Hooks specification
Questions about the VectorCare MCP server
- What is an MCP server?
- MCP means Model Context Protocol. It is an open standard that lets an AI agent call tools in other software. An MCP server is the software that offers those tools. We design the VectorCare MCP server to give agents tools for patient transport, such as finding options and booking a ride.
- Can my team use the VectorCare MCP server yet?
- Not yet. We are designing it now, and we want to shape it with the teams that will use it. If you build agents or run patient transport, talk to us.
- How does the MCP server relate to the VectorCare open API?
- The open API is the foundation. The MCP server is a thin wrapper over the open API spec, so each API function can become a tool for agents. Our SMART on FHIR app and web app sit on the same API.
- How does this relate to Epic Connectors?
- Epic announced Connectors on October 21, 2026, and built them first on MCP. Epic plans to show developer Connectors on Epic Showroom from March 2027. We are designing the VectorCare MCP server so that it can become an Epic Connector. It is also for agents outside Epic, such as agents in care coordination products and care apps.
- Which AI model does it use?
- The MCP server does not pick or run a model. It answers tool calls. The team that builds the agent picks the model.
- Is VectorCare a transport broker?
- No. VectorCare is the software rails for patient transport. A program can keep its broker or go direct. Either way, the request runs on VectorCare.
Build with us
Do you build agents for a health system, run a dispatch system or make a care app? Tell us what your agents need to do. We will talk through the design with you.
Talk to us
Or to use the form here.
Using Epic? Read about VectorCare and Epic Connectors
Epic, Epic Showroom and Connectors are trademarks of Epic Systems Corporation. VectorCare is not affiliated with or endorsed by Epic.