Tebra MCP connector
The Tebra connector lets Claude, ChatGPT, Cursor, or the Elaichi Agent read patients, encounters, conditions, care plans, and other clinical records from Tebra, with each person signed in as themselves and every lookup logged.
-
How it connects. OAuth or API key. 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.
54 tools
How to connect
How to connect Tebra to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Tebra once
-
Open Connections, choose Add connection, and pick Tebra.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Tebra app, then approve. Tebra 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.
Tebra 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.
Tebra 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.
Tebra 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 Tebra 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 Tebra through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Front desk
Pull up a patient before they arrive
Ask for a patient by name and get their recent encounters, allergies, and care team in one answer, so the check-in conversation starts informed.
-
Clinical
Review a chart in plain language
Before a visit, ask what conditions, observations, and immunizations are on file for a patient in Tebra and get a readable rundown instead of clicking through tabs.
-
Care coordination
Find patients with no care plan
List patients carrying an active condition and check which of them have a care plan and a named care team, then follow up with the gaps.
-
Quality
Check immunization coverage across the panel
Ask which patients seen this quarter have an immunization record and which do not, and get a list you can act on without exporting anything.
-
Billing
Confirm encounters before claims go out
Look up the encounters and diagnostic reports tied to a patient to confirm a visit happened and what it covered before a claim is prepared.
-
Practice management
Answer questions about the week's visits
Ask how many encounters took place, which providers' care teams were involved, and which document references were added, and get the numbers from live Tebra records.
Try asking
- “List patients with an encounter this week and their care teams.”
- “Which patients have an active diabetes condition but no care plan?”
- “Show immunizations on file for the patients seen yesterday.”
Compare
Elaichi vs Zapier MCP vs Composio for Tebra
All three can connect Tebra 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 Tebra tools | Allow or restrict single Tebra 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 Tebra 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
Tebra tools for your AI agents
54 tools are ready to call through Elaichi's MCP endpoint the moment you connect Tebra, 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 Tebra gets you
6 screens from the product, each doing one job for your Tebra account.
The agent
Ask about any Tebra patient in plain words.
Encounters, conditions, and care plans answered from live Tebra records, no chart clicking required.
- patients
- encounters
- conditions
- observations
Ask Elaichi to work across your apps.
List patients with an encounter this week and their care teams.
Which patients have an active diabetes condition but no care plan?
Show immunizations on file for the patients seen yesterday.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Tebra in Claude, ChatGPT, and Cursor, connected once.
One governed endpoint for the whole organization, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
54 Tebra tools, no custom code to write.
Patients, encounters, conditions, immunizations, and observations covered the moment Tebra is connected.
- List all Tebra patients
- Get single Tebra patient by ID
- List all Tebra allergy intolerances
- Get single Tebra allergy intolerance by ID
ElaichiToolsToolboxes
Every team gets its own Tebra toolbox.
Front desk, clinical, and billing each work from a toolbox scoped to their job.
- Front desk
- Clinical
- Care coordination
- Quality
ElaichiToolboxesShared connections
Share Tebra access without sharing a secret.
One person connects Tebra, teammates work through it, and nobody else sees a credential.
- Front desk
- Clinical
- Care coordination
- Quality
ElaichiConnectionsAudit log
Know who opened which Tebra patient record.
Every lookup logged with who, when, what happened, and which record was read.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 starts real Tebra work on its own.
Encounters fetched, grouped, drafted into a digest, approved by a person, then posted back.
Tebra digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch patients
Tebra
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
Tebra
Queued
Collections and dashboards
Tebra numbers that arrive without being asked for.
Encounters and patients counted on a schedule, broken down by team, with no model in the math.
Tebra health
Refreshed 4 minutes ago · every 15 minutes · from the patients collection
Patients
1,284 ↓ 12%
Encounters
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Patients created
Last 14 days
By team
Share of activity
Front desk 34%
Clinical 27%
Care coordination 21%
Quality 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Tebra to Claude?
Connect Tebra in Elaichi first. Tebra uses OAuth or an API key, and this connector needs an OAuth application registered inside your Tebra account, so someone has to bring a client ID and secret once during setup, after which nobody touches them again. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Tebra records are available in your conversation.
Does Tebra work with ChatGPT and Cursor as well as Claude?
Yes. Once Tebra is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Tebra once and every client picks it up.
What can an AI agent actually do with my Tebra data?
It can look things up. An agent can find a Tebra patient and read their encounters, conditions, allergies, care plans, care teams, goals, immunizations, observations, diagnostic reports, document references, and devices, then answer your question or summarize what it found. This connector reads Tebra records and does not change them. Short, concrete asks such as a patient name plus what you want to know work better than long paragraphs.
Does connecting Tebra give the AI access to every patient record?
No. Every request runs under the Tebra sign-in of the person asking, so the agent sees only the patients and records that person can already open in Tebra. Elaichi can narrow that further, for example keeping diagnostic reports out of reach for a front desk team, but it can never widen what Tebra itself allows.
Can I stop an agent from deleting or changing things in Tebra?
This Tebra connector only reads records, so there is nothing for an agent to delete or edit. Restrictions still apply per action, so you can take any lookup away, such as reading observations or document references, for a particular team. A restricted action is left out of the tool list the AI client sees and cannot be called, whatever the prompt says.
What happens to a Tebra connection when someone leaves?
Offboarding a person in Elaichi ends their access to Tebra through every connected client at once. A Tebra connection they shared keeps working for everyone else on the team. If you want the connection gone entirely, disconnect Tebra once in Elaichi and it disappears from Claude, ChatGPT, Cursor, and every other client together.
Does the Tebra MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Tebra 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 Tebra?
Yes. Both let Claude, ChatGPT or Cursor use Tebra. 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 Tebra call.
How is Elaichi different from Composio for Tebra?
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 Tebra: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Tebra 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.