Tebra vs Tx Medical Exclusions
A side-by-side look at the Tebra and Tx Medical Exclusions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tebra for biology & bioinformatics work as a local process; choose Tx Medical Exclusions for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tebra when
- You need dedicated capabilities in the Biology & 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.
Choose Tx Medical Exclusions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Legal |
| Quality signal | 55/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | TEBRA_SOAP_USERTEBRA_SOAP_PASSWORDTEBRA_CUSTOMER_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 47 | Not listed |
| Full listing | View Tebra | View Tx Medical Exclusions |
Tools & capabilities
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
Tx Medical Exclusions tools
No tool names declared yet. Check the project README from 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.
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"
}
}
}
}
Tx Medical Exclusions
{
"mcpServers": {
"tx-medical-exclusions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tx-medical-exclusions"
]
}
}
}
Frequently asked questions
Tebra is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Tx Medical Exclusions belongs to Legal and uses a local stdio subprocess. Pick Tebra for biology & bioinformatics work and Tx Medical Exclusions for legal.
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.
Tebra has no declared pricing — check the project's own site. Tx Medical Exclusions is listed as free. Auth: no auth required. 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 tebra and tx-medical-exclusions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tebra has a quality signal of 55/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Tx Medical Exclusions has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.