MCP server for Tebra/Kareo practice management — patients, billing, scheduling, FHIR (45 tools)
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"com-jamesrosingmd-tebra": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Tebra (formerly Kareo) practice management. Connects your existing Tebra account to Claude and other MCP-compatible AI agents, exposing 33 SOAP tools and 12 FHIR clinical tools for patients, encounters, appointments, billing, documents, insurance, and clinical data. No data is accessible without valid Tebra API credentials.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / finance
Persistent memory using a knowledge graph
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
a self-hosted project management & Kanban solution + Instant shareable boards
All-in-one local AI hub for Obsidian — LLM chat with vault tools, MCP servers, RAG, workflow automation, encryption, and edit history. Fully private, no cloud required.
MCP Security Weekly
Get CVE alerts and security updates for com.jamesrosingmd/tebra and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for Tebra (formerly Kareo) practice management. Connects your existing Tebra account to Claude and other MCP-compatible AI agents, exposing 33 SOAP tools and 12 FHIR clinical tools for patients, encounters, appointments, billing, documents, insurance, and clinical data. No data is accessible without valid Tebra API credentials.
npx tebra-mcp-server
| Variable | Required | Description |
|---|---|---|
TEBRA_SOAP_USER | Yes | SOAP API user (email) |
TEBRA_SOAP_PASSWORD | Yes | SOAP API password |
TEBRA_CUSTOMER_KEY | Yes | Customer key from Tebra PM admin |
TEBRA_SOAP_ENDPOINT | No | Override SOAP endpoint (for testing) |
| Variable | Required | Description |
|---|---|---|
TEBRA_FHIR_CLIENT_ID | For FHIR | OAuth2 client ID from Tebra developer portal |
TEBRA_FHIR_CLIENT_SECRET | For FHIR | OAuth2 client secret |
TEBRA_FHIR_BASE_URL | No | FHIR R4 base URL (defaults to Tebra production) |
FHIR credentials are obtained from the Tebra Developer Portal under API > FHIR Access. The server uses OAuth2 client credentials flow with automatic token caching and refresh.
Add to .mcp.json in your project root:
{
"mcpServers": {
"tebra": {
"command": "npx",
"args": ["-y", "tebra-mcp-server"],
"env": {
"TEBRA_SOAP_USER": "user@practice.com",
"TEBRA_SOAP_PASSWORD": "your-password",
"TEBRA_CUSTOMER_KEY": "your-customer-key",
"TEBRA_FHIR_CLIENT_ID": "optional-fhir-client-id",
"TEBRA_FHIR_CLIENT_SECRET": "optional-fhir-client-secret"
}
}
}
}
Add to your claude_desktop_config.json:
{
"mcpServers": {
"tebra": {
"command": "npx",
"args": ["-y", "tebra-mcp-server"],
"env": {
"TEBRA_SOAP_USER": "user@practice.com",
"TEBRA_SOAP_PASSWORD": "your-password",
"TEBRA_CUSTOMER_KEY": "your-customer-key"
}
}
}
}
Add to your MCP settings:
{
"mcpServers": {
"tebra": {
"command": "npx",
"args": ["-y", "tebra-mcp-server"],
"env": {
"TEBRA_SOAP_USER": "user@practice.com",
"TEBRA_SOAP_PASSWORD": "your-password",
"TEBRA_CUSTOMER_KEY": "your-customer-key"
}
}
}
}
| Tool | Description |
|---|---|
tebra_search_patients | Search patients by name, DOB, MRN, or external ID (20+ filters) |
tebra_get_patient | Get full patient record with insurance, cases, and authorizations |
tebra_create_patient | Register a new patient with demographics and insurance |
tebra_update_patient | Update patient demographics, contact info, or insurance |
tebra_get_all_patients | Bulk patient retrieval with pagination (for sync operations) |
| Tool | Description |
|---|---|
tebra_get_appointments | Search appointments by date range, provider, or patient |
tebra_get_appointment_detail | Get full appointment detail including reason, notes, and history |
tebra_create_appointment | Create an appointment (requires provider, location, reason IDs) |
tebra_update_appointment | Update, reschedule, or cancel an existing appointment |
tebra_delete_appointment | Permanently delete an appointment |
tebra_get_appointment_reasons | List configured appointment |