Oracle Health MCP connector
The Oracle Health connector brings patients, appointments, observations, charge items and care goals into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person works with Oracle Health records inside their own access, with every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Oracle Health to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Oracle Health once
-
Open Connections, choose Add connection, and pick Oracle Health.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Oracle Health app, then approve. Oracle Health needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Oracle Health MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Oracle Health MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Oracle Health MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Oracle Health to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Oracle Health through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Front desk
Book the follow-up before the patient leaves
Ask for the next open slot, create the appointment in Oracle Health, and move it later if the patient calls back. The schedule stays current without opening a second screen.
-
Care coordination
See which goals are still open
Pull a patient's care goals from Oracle Health and ask which ones have no progress logged. Then record the outreach as a communication so the next coordinator knows it happened.
-
Billing
Check charge items before the claim goes out
List the charge items on a visit, compare them with the patient's insurance plan, and correct a line in Oracle Health when a modifier is missing.
-
Registration
Register a new patient from the intake form
Create the patient in Oracle Health with the details from the form, then update the record when the address or phone number changes at check-in.
-
Nursing
Record the reading as soon as it is taken
Update a blood pressure or weight observation in Oracle Health from a plain sentence, and confirm the latest value for a patient before the clinician walks in.
-
Care management
Log every outreach call in one place
After a call with a patient or family member, create the communication in Oracle Health with who was reached and what was agreed, so the chart tells the whole story.
Try asking
- “Show tomorrow's appointments for the cardiology clinic”
- “Which patients have care goals with no progress this month?”
- “List charge items on yesterday's visits missing an insurance plan”
Compare
Elaichi vs Zapier MCP vs Composio for Oracle Health
All three can connect Oracle Health to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Oracle Health tools | Allow or restrict single Oracle Health tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Oracle Health call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Oracle Health tools for your AI agents
128 tools are ready to call through Elaichi's MCP endpoint the moment you connect Oracle Health, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Oracle Health gets you
6 screens from the product, each doing one job for your Oracle Health account.
The agent
Ask about appointments and get live answers.
Patients, appointments, goals and charge items from Oracle Health, answered in plain language.
- patients
- appointments
- observations
- charge items
Ask Elaichi to work across your apps.
Show tomorrow's appointments for the cardiology clinic
Which patients have care goals with no progress this month?
List charge items on yesterday's visits missing an insurance plan
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Oracle Health from any client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
128 tools cover Oracle Health without custom code.
Patients, appointments, observations, communications and charge items, ready the day you connect.
- Get single Oracle Health goal by ID
- List all Oracle Health goals
- List all Oracle Health people
- Get single Oracle Health person by ID
Toolboxes
Every team gets its own Oracle Health toolbox.
Front desk books appointments, billing reviews charge items, nursing records observations.
- Front desk
- Care coordination
- Billing
- Registration
Shared connections
Share one Oracle Health connection, not credentials.
One person connects, teams and members work through it, nobody else sees a secret.
- Front desk
- Billing office
- Care team
- Nursing
Audit log
Every Oracle Health call names who made it.
When, who, what happened and which patient or appointment, in an append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fetches appointments and drafts the digest.
Appointments are grouped, an agent writes the summary, a person approves, Oracle Health gets the note.
Oracle Health digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch patients
Oracle Health
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Oracle Health
Queued
Collections and dashboards
Oracle Health numbers refresh without anyone asking.
Patients registered, appointments booked and charge items added, by team, with no model involved.
Oracle Health health
Refreshed 4 minutes ago · every 15 minutes · from the patients collection
Patients
1,284 ↓ 12%
Appointments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Patients created
Last 14 days
By team
Share of activity
Front desk 34%
Billing office 27%
Care team 21%
Nursing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Oracle Health to Claude?
Connect Oracle Health in Elaichi first. Oracle Health requires an OAuth application registered on its own side, so one person brings that client ID and secret into Elaichi once, then signs in to Oracle Health as themselves. After that, open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Nobody else on the team has to generate a client ID or secret, they simply sign in.
Does Oracle Health work with ChatGPT and Cursor as well as Claude?
Yes. Once Oracle Health is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Oracle Health once and every client picks it up.
What can an AI agent actually do with my Oracle Health data?
With Oracle Health connected, you can ask who is on tomorrow's schedule, book or move an appointment, look up a patient, register a new one, update an observation, log a communication, check a patient's insurance plan and review charge items on a visit. Short, specific asks such as "move Mrs. Rivera's 2pm to Thursday" work better than long paragraphs.
Does connecting Oracle Health give the AI access to every patient record?
No. Every call into Oracle Health runs as the person who signed in, so the AI can only reach the patients, appointments and charge items that person could already open in Oracle Health. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Oracle Health itself allows.
Can I stop an agent from deleting or changing things in Oracle Health?
This connector does not delete anything in Oracle Health at all. For changes, restrictions in Elaichi work per action, so you can allow reading patients and appointments while blocking creating or updating them. A restricted action is left out of the AI client's list entirely and cannot be called, whatever the prompt says.
What happens to an Oracle Health connection when someone leaves?
Offboarding a person in Elaichi ends their access to Oracle Health through every client at once. A shared Oracle Health connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Oracle Health once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Oracle Health MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Oracle Health is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Oracle Health?
Yes. Both let Claude, ChatGPT or Cursor use Oracle Health. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Oracle Health call.
How is Elaichi different from Composio for Oracle Health?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Oracle Health: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Oracle Health in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.