Clinicaltables vs Langcare MCP Fhir
A side-by-side look at the Clinicaltables and Langcare MCP Fhir MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clinicaltables for biology & bioinformatics work as a local process; choose Langcare MCP Fhir for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clinicaltables when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
conditions, icd10cm, icd9cm.
Choose Langcare MCP Fhir when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 57/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 67 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Clinicaltables | View Langcare MCP Fhir |
Tools & capabilities
Clinicaltables tools 10
conditions"What is [condition]" / "look up medical condition by name" / "find a disease called [X]" / "patient-friendly medical term for [Y]" — search the NLM patient-friendly medical conditions vocabulary (~700 common conditions written for lay readers). Returns canonical names like "Migraine", "Type 2 diabetes". Use for symptom-to-condition lookup, intake forms, or simplifying clinical text for patients.icd10cm"What's the ICD-10 code for [diagnosis]" / "diagnosis code lookup" / "billing code for [condition]" / "EHR code for [X]" — search ICD-10-CM diagnostic codes (US clinical modification, ~96k codes). Returns code + full description. Use for medical billing, EHR diagnosis coding, claim coding. Example: terms="diab" → E11.9 Type 2 diabetes mellitus without complications.icd9cm"Old ICD-9 code for [diagnosis]" / "pre-2015 diagnosis codes" — search legacy ICD-9-CM diagnostic codes. Use ONLY when working with pre-2015 US clinical records; new claims must use icd10cm. Same shape as icd10cm.procedures"What is the procedure called [X]" / "medical procedure name lookup" / "patient-friendly name for [surgery]" — search clinical procedure names (NLM curated, ~7k entries). Returns short names like "Appendectomy", "Knee replacement". Patient-facing language; use for forms or intake screens. This vocabulary is SMALL and curated, so common terms can legitimately miss ("colonoscopy" and "MRI" both return 0, verified 2026-09-16) — a no_match here means "not in this list", not "no such procedure". For billing codes use icd10cm or a CPT source instead.drugs"Drug name lookup" / "find prescription [X]" / "medication autocomplete" / "RxCUI for [drug]" / "what does [pill] treat" / "available strengths for [drug]" — search RxTerms (NLM prescribing-vocabulary derived from RxNorm, ~22k drug names with route/strength). Returns names like "Aspirin (Chewable)", "Lisinopril (Oral Pill)". Use for prescription entry, drug name autocomplete, or as a stepping-stone to RxNorm RxCUI lookups. Pass ef="STRENGTHS_AND_FORMS,RXCUIS" to include dosage strengths and RxNorm IDs.loinc"LOINC code for [lab test]" / "standard code for blood test [X]" / "lab result identifier lookup" / "normalize lab name [Y]" — search LOINC lab test codes (Logical Observation Identifiers Names and Codes, universal lab test identifiers). Returns codes like "2093-3 Cholesterol [Mass/Vol] Ser/Plas". Use when normalizing lab results across institutions.npi_individual"Find a doctor / clinician / physician by name" / "look up NPI for [provider]" / "verify a doctor's credentials" / "what's [Dr. X]'s NPI" — search the NPPES National Provider Identifier registry for individual US healthcare providers (~5M entries). Returns NPI numbers + provider names. terms can be a name fragment, NPI, or specialty. Use ef to include address, specialty, gender.npi_organization"Find a hospital / clinic by name" / "look up NPI for [organization]" / "what's [Mayo Clinic]'s NPI" / "verify a healthcare facility" — search the NPPES NPI registry for organizational providers (~1.8M entries) — hospitals, clinics, group practices. Same shape as npi_individual. terms can be org name, NPI, or city.ucum"Unit of measure code for [X]" / "standard UCUM unit for [Y]" / "mg/dL code" — search UCUM (the Unified Code for Units of Measure, used by FHIR, LOINC, and most modern health-IT systems). Returns codes like "mg/dL", "[in_i]" (inch). Use when normalizing lab result units or rendering measurements.disease_names"UMLS code for [disease]" / "clinical name for rare disease [X]" / "look up a syndrome by name" / "find CUI for [condition]" — search the NLM Disease Names vocabulary (UMLS-derived, broader than `conditions`; includes rare diseases, syndromes, clinical terminology, ~12k entries). Returns UMLS CUIs (e.g., C0011860) plus canonical names. Use when you need clinical-grade vocabulary linkage rather than patient-friendly labels.
Langcare MCP Fhir 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.
Clinicaltables
{
"mcpServers": {
"clinicaltables": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-clinicaltables"
]
}
}
}
Langcare MCP Fhir
{
"mcpServers": {
"langcare-mcp-fhir": {
"command": "npx",
"args": [
"-y",
"@langcare/langcare-mcp-fhir"
]
}
}
}
Frequently asked questions
Clinicaltables is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Langcare MCP Fhir belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick Clinicaltables for biology & bioinformatics work and Langcare MCP Fhir for biology & 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.
Clinicaltables has no declared pricing — check the project's own site. Langcare MCP Fhir 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 clinicaltables and langcare-mcp-fhir as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clinicaltables has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Langcare MCP Fhir has 43/100 (Fair) with 1 views, 0 installs and 67 GitHub stars.