Medplum MCP vs Tebra
A side-by-side look at the Medplum MCP and Tebra MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Medplum MCP for biology, medicine and bioinformatics work; choose Tebra for biology, medicine and bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Medplum MCP when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
Choose Tebra when
- You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TEBRA_SOAP_USER, TEBRA_SOAP_PASSWORD, TEBRA_CUSTOMER_KEY. - You want tools like
tebra_search_patients, tebra_get_patient, tebra_create_patient.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology, Medicine and Bioinformatics | Biology, Medicine and Bioinformatics |
| Quality signal | 41/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | TEBRA_SOAP_USERTEBRA_SOAP_PASSWORDTEBRA_CUSTOMER_KEY |
Tools & capabilities
Medplum MCP tools
No tool names declared yet. Check the project README from the listing page.
Tebra tools 47
tebra_search_patientsSearch patients by name, DOB range, insurance, practice, and more (16 server-side filters)tebra_get_patientGet full patient record (by Tebra ID or external ID) with cases, insurance policies, and authorizationstebra_create_patientRegister a new patient with demographics, insurance, and guarantortebra_update_patientUpdate patient demographics and contact infotebra_get_all_patientsBulk patient retrieval with pagination (for sync operations)tebra_get_appointmentsSearch appointments by date range, resource (provider), patient, status, locationtebra_get_appointment_detailGet full appointment detail including recurrence, group data, and resourcestebra_create_appointmentCreate an appointment (provider, location, start time + duration/end)tebra_update_appointmentUpdate or reschedule an existing appointmenttebra_update_appointment_statusChange only the status (Confirmed, CheckedIn, NoShow, Cancelled, ...)tebra_delete_appointmentPermanently delete an appointmenttebra_get_appointment_reasonsList configured appointment types/reasons for the practice- +35 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Medplum MCP
No confirmed install command for Medplum MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Tebra
{
"mcpServers": {
"tebra": {
"command": "npx",
"args": [
"-y",
"tebra-mcp-server"
],
"env": {
"TEBRA_SOAP_USER": "YOUR_TEBRA_SOAP_USER_HERE",
"TEBRA_SOAP_PASSWORD": "YOUR_TEBRA_SOAP_PASSWORD_HERE",
"TEBRA_CUSTOMER_KEY": "YOUR_TEBRA_CUSTOMER_KEY_HERE"
}
}
}
}
Frequently asked questions
Medplum MCP is categorized under Biology, Medicine and Bioinformatics and uses an install path we have not confirmed yet. Tebra belongs to Biology, Medicine and Bioinformatics and uses a local stdio subprocess. Pick Medplum MCP for biology, medicine and bioinformatics work and Tebra for biology, medicine and bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Medplum MCP has no confirmed install command yet — follow its own setup instructions.
Medplum MCP has no declared pricing — check the project's own site. Tebra has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-112 and tebra as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Medplum MCP has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 2,736 GitHub stars. Tebra has 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars.