Tebra
Connect Tebra (Kareo) practice management—patients, billing, scheduling, and FHIR—to your coding agent via npm stdio MCP.
Overview
com.jamesrosingmd/tebra is a Build-phase MCP server that exposes 45 Tebra/Kareo practice management tools—including patients, billing, scheduling, and FHIR—over npm stdio.
What is this MCP server?
- npm package tebra-mcp-server v0.2.5 with stdio MCP transport
- 45 tools covering patients, billing, scheduling, and FHIR-oriented workflows
- Requires TEBRA_SOAP_USER, TEBRA_SOAP_PASSWORD, and TEBRA_CUSTOMER_KEY
- Targets Tebra / Kareo practice management APIs
- Open-source server at github.com/jamesrosing/tebra-mcp-server
- 45 MCP tools per server description
- npm package tebra-mcp-server version 0.2.5
- Three required secret env vars: TEBRA_SOAP_USER, TEBRA_SOAP_PASSWORD, TEBRA_CUSTOMER_KEY
Community signal: 1 GitHub stars.
What problem does it solve?
Healthcare builders waste time hand-rolling Tebra SOAP calls and FHIR glue when agents could call a typed MCP tool surface instead.
Who is it for?
Solo developers or micro-teams building Tebra-connected practice workflows who already have legitimate Tebra API access and compliance guardrails.
Skip if: General-purpose SaaS with no Tebra tenant, or anyone without secure handling of PHI and Tebra credentials.
What do I get? / Deliverables
Once npm tebra-mcp-server is configured with your Tebra secrets, your agent can invoke practice management operations through MCP during development.
- Stdio MCP server wired to your Tebra tenant
- Access to 45 documented practice management tools from the agent
- Faster Build-phase Tebra automations without manual SOAP scripting
Recommended MCP Servers
Journey fit
Healthcare admin SaaS and automation projects need live EHR and practice data during implementation, which is classic Build-phase integration work. SOAP credentials and customer keys configure a backend MCP bridge (tebra-mcp-server on npm), not a ship-time security audit skill.
How it compares
Tebra SOAP/FHIR MCP integration with 45 tools, not a generic FHIR tutorial skill or a hosted EHR product.
Common Questions / FAQ
Who is com.jamesrosingmd/tebra for?
Builders automating or extending Tebra/Kareo practice management who use MCP-capable agents and can supply SOAP user, password, and customer key for a practice.
When should I use Tebra MCP?
Use it in Build when you are implementing patient, billing, scheduling, or FHIR features against a live Tebra practice and want agent-driven API access via stdio MCP.
How do I add com.jamesrosingmd/tebra to my agent?
Install or run the npm package tebra-mcp-server, set TEBRA_SOAP_USER, TEBRA_SOAP_PASSWORD, and TEBRA_CUSTOMER_KEY in the MCP server env, register stdio in your agent config, and restart the client.