Medical Terminologies MCP vs Tebra

In-depth architectural comparison of the Medical Terminologies MCP and Tebra MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Medical Terminologies MCP when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: WHO_API_KEY, SNOWSTORM_URL, SNOWSTORM_AUTH.
• Primary tools included: icd11_search, icd11_lookup, icd11_hierarchy.

Explore Medical Terminologies MCP Details

Choose Tebra when:

• You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: tebra_search_patients, tebra_get_patient, tebra_create_patient.

Feature & Specification Comparison

Specification	Medical Terminologies MCP SidneyBissoli Biology, Medicine and Bioinformatics	Tebra Biology, Medicine and Bioinformatics
Summary	Unified MCP server for ICD-11 (WHO), LOINC, RxNorm, MeSH (NLM), ATC, CID-10 (Brazilian DataSUS), and optional SNOMED CT. 28 tools (34 with SNOMED) with structuredContent + outputSchema on every default tool. Hosted on Cloudflare Workers, listed on Smithery, and on npm.	MCP server for Tebra/Kareo practice management — patients, billing, scheduling, FHIR (45 tools)
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "sidneybissoli-medical-terminologies-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sidneybissoli-medical-terminologies-mcp"
      ],
      "env": {
        "WHO_API_KEY": "YOUR_WHO_API_KEY_HERE",
        "SNOWSTORM_URL": "YOUR_SNOWSTORM_URL_HERE",
        "SNOWSTORM_AUTH": "YOUR_SNOWSTORM_AUTH_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "tebra": {
      "command": "npx",
      "args": [
        "-y",
        "tebra-mcp-server"
      ]
    }
  }
}

Related MCP Server Comparisons