Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Tebra to Claude Code

Make Claude book appointments and update patient demographics in Tebra. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Tebra to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Tebra, you add a Tebra MCP server: a small hosted service that exposes Tebra's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Tebra account. No API keys pasted into config files.

claude mcp add --transport http tebra https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Tebra once connected?

Full read-write Tebra access lets Claude book and reschedule appointments, add or update patient demographics, create encounters, draft and route claims, and post payments, all after you approve. The scheduling, intake, and billing follow-up that used to mean clicking through screens happen where the practice data already lives.

  • Book, reschedule, or cancel an appointment on a provider's calendar
  • Add or update patient demographics and contact details on a record
  • Create an encounter from a visit and record its charges
  • Draft a claim from a visit and route it for review before submission
  • Look up a patient's outstanding balance and prepare a billing follow-up
  • Find all appointments matching a query and propose batched updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Tebra access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Tebra API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Tebra changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Tebra connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Tebra connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Tebra account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Tebra's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Tebra?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Tebra account it signs in with. Revoking access is one click in Tebra.

More on the Tebra connector

Tebra connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us