MCP · AI assistants
AI assistant connection (MCP), in preparation
Chivo is preparing an MCP connection for AI assistants. It is not enabled yet: we will first publish its scope and documentation here, and it will only work with your clinic administrator's authorization.
Status: no published capabilities
What is MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants such as Claude or ChatGPT connect to external tools after the user authorizes them.
This way, the assistant can use another service within what has been authorized, without you having to copy and paste information.
Learn about the standard at modelcontextprotocol.io (opens in a new tab)Status
Chivo's MCP connection does not have published capabilities yet. We will publish its scope and documentation here before enabling it.
Until that documented authorization flow exists, do not send real clinical information to AI services.
Authorization principles
Conditions Chivo will meet before enabling any MCP connection.
The clinic administrator authorizes
The connection is only enabled when your clinic administrator authorizes it.
Permissions per scope
If the connection ever handles identifiable patient data, each scope will require its own permission.
Access log
If the connection ever handles identifiable patient data, it will require an access log.
Review with each AI provider
If identifiable patient data is involved, data processing will first be reviewed with each AI provider.
No clinical data outside that flow
Real clinical information should not be sent to AI services without that documented authorization flow.
How the connection would work
This is how MCP connectors generally work in AI assistants. Chivo-specific steps will be documented on this page.
1. Add the connector
From your AI assistant's settings, you add the service's connector.
2. Sign in and authorize
You sign in to the service and review which scopes you grant before accepting.
3. Ask questions
The assistant queries the service only within the authorized scopes.
4. Remove the connector
AI assistants generally let you remove a connector from their settings.
What a conversation could look like
With sample data and no identifiable patient information.
Transcript of the simulated conversation
- You: How many appointments are there tomorrow at Example Clinic?
- Assistant: There are 12 appointments scheduled tomorrow: 7 in the morning and 5 in the afternoon.
- You: How many of today's appointments are finished?
- Assistant: Of today's 9 appointments, 4 are finished, 1 is on visit and 2 are waiting; 1 patient did not show up and 1 appointment was cancelled.
- You: And the phone number of the 9:00 am patient?
- Assistant: This simulated connection does not include identifiable patient data. That access would need its own permission, authorized by your clinic administrator.
It illustrates the kind of conversation that could be possible. It does not describe available capabilities.
Do you build integrations?
Chivo's technical documentation will be gathered on the developers page. If you want to see Chivo from the inside, book a demo with the team.
Questions about MCP
Who authorizes the connection?
Your clinic administrator. No MCP connection will be enabled without their authorization.
What data will the assistant be able to access?
There are no published capabilities yet. We will publish the scope on this page before enabling the connection. If it ever includes identifiable patient data, it will require permissions per scope, an access log and a review of data processing with each AI provider.
When will it be available?
There is no published date yet. Write to us and we will let you know.
Get started with Chivo
Three steps, no charges before you have access.
1. Book a demo
We review how you work and answer your questions.
2. Pick your plan
You add your card; nothing is charged yet.
3. We activate your access
The team sets up your clinic and your trial starts that day.