tebra-mcp-server

MCP server for Tebra (formerly Kareo) practice management. Connects your existing Tebra account to Claude and other MCP-compatible AI agents, exposing 34 SOAP tools and 13 FHIR clinical tools for patients, encounters, appointments, billing, documents, insurance, and clinical data. Every request body is generated from the live Tebra WSDL contract (member names and sequence order verified against KareoServices.svc?xsd=xsd0/xsd7), with a regression suite locking the wire format in place. No data is accessible without valid Tebra API credentials.

This is an independent open-source project. It is not affiliated with, endorsed by, or supported by Tebra Technologies, Inc.; "Tebra" and "Kareo" are trademarks of their owner, used here only to identify the API this server talks to. Tool results contain protected health information: sending them to Claude requires a Claude plan under which Anthropic signs a Business Associate Agreement (BAA). Consumer Claude plans are not covered, and confirming coverage is the responsibility of the practice operating the server.

Hosted version available

Do not want to manage credentials, hosting, and updates yourself? DOCK is the managed version of this server: encrypted per-practice auth, audit logs, draft-first write actions, and a workflow library. Founding practices lock lifetime pricing: Front Desk $49/mo (Zenoti), Billing Desk $99/mo (Tebra; DOCK signs its own BAA with the practice, separate from Anthropic's), Full Practice $129/mo (both). https://dockhq.vercel.app

Quick Start

npx tebra-mcp-server

Prerequisites

• Node.js 18+
• Tebra SOAP API credentials (generated in Tebra PM admin under Settings > API)
• (Optional) Tebra FHIR API credentials for clinical data access

Environment Variables

SOAP API (required)

FHIR API (optional -- enables 13 clinical data tools)

FHIR credentials are obtained through Tebra appSphere. The server uses the OAuth2 client credentials flow with automatic token caching, refresh 60s before expiry, and a one-shot retry on 401. Two client authentications are supported: SMART Backend Services private_key_jwt (an appSphere Backend App registered as "Confidential (URL for JWKS)" — the server signs an RS384 client assertion with iss=sub=client id, aud=token URL, a 5-minute exp and a unique jti, sent as client_assertion with client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer; the private key is read from disk once and never transmitted) and the legacy client_secret flow. Set the key path for the former, the secret for the latter. Note: both the practice and the backend-service client must be activated by Tebra Customer Care before tokens are issued — a 401 can mean "not yet activated" rather than "bad credentials".

Installation

Claude Code

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"
      }
    }
  }
}

Claude Desktop

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"
      }
    }
  }
}

Cursor / VS Code

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"
      }
    }
  }
}

Available Tools (47 total)

Patient Management

Appointments

Encounters & Billing

Insurance & Authorizations

Practice Configuration

Documents

Financial Analysis

External Vendor & System

FHIR Clinical Data (requires FHIR credentials)

These tools access clinical data via the Tebra FHIR R4 API. They require separate FHIR credentials (see Environment Variables above). If FHIR credentials are not configured, these tools will not be registered.

FHIR patient IDs are a different identifier space from SOAP patient IDs — use tebra_fhir_search_patients to resolve them. All FHIR searches follow Bundle pagination automatically (up to 10 pages), and the three resources where Tebra requires a second search parameter (MedicationRequest intent, CarePlan category, CareTeam status) get sensible defaults so they don't silently return empty.