In-depth architectural comparison of the Fhir MCP Server and Dicom Hl7 MCP Server 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.
At a Glance & Executive Verdict
Fhir MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Dicom Hl7 MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Fhir MCP Server if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Dicom Hl7 MCP Server if your workspace requires Biology, Medicine and Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Fhir MCP Server 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: FHIR_SERVER_BASE_URL, FHIR_SERVER_CLIENT_ID, FHIR_SERVER_CLIENT_SECRET, FHIR_SERVER_SCOPES, FHIR_SERVER_DISABLE_AUTHORIZATION, FHIR_MCP_HOST, FHIR_MCP_PORT.
Model Context Protocol server for Fast Healthcare Interoperability Resources (FHIR) APIs. Provides seamless integration with FHIR servers, enabling AI assistants to search, retrieve, create, update, and analyze clinical healthcare data with SMART-on-FHIR authentication support.
The only MCP server bridging DICOM, HL7v2, and FHIR in one package. Cross-standard mapping, Mirth Connect channel generation, vendor private tag decoding (GE, Siemens, Philips), and integration pattern knowledge. Built by a 19-year healthcare IT veteran. pip install dicom-hl7-mcp
Category & Scope
Tools & Capabilities Breakdown
Fhir MCP Server Tools (13)
get_capabilities
Retrieves metadata about a specified FHIR resource type, including its supported search parameters and custom operations.
type
The FHIR resource type name (e.g., "Patient", "Observation", "Encounter")
search
Executes a standard FHIR search interaction on a given resource type, returning a bundle or list of matching resources.
searchParam
A mapping of FHIR search parameter names to their desired values (e.g., {"family":"Simpson","birthdate":"1956-05-12"}).
response_filter_fhirpaths
(Optional) An array of FHIRPath expressions (e.g., `["Patient.name", "Patient.birthDate", "Bundle.link.where(relation='next').url"]`) to apply to the resources in the response bundle.
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).
Fhir MCP Server is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Dicom Hl7 MCP Server belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Fhir MCP Server when you need capabilities focused on biology, medicine and bioinformatics and Dicom Hl7 MCP Server when you require tools for biology, medicine and bioinformatics.
Performs a FHIR "read" interaction to retrieve a single resource instance by its type and resource ID, optionally refining the response with search parameters or custom operations.
id
The logical ID of a specific FHIR resource instance.
operation
The name of a custom FHIR operation or extended query defined for the resource (e.g., "$everything").
create
Executes a FHIR "create" interaction to persist a new resource of the specified type.
payload
A JSON object representing the full FHIR resource body to be created.
update
Performs a FHIR "update" interaction by replacing an existing resource instance's content with the provided payload.
delete
Execute a FHIR "delete" interaction on a specific resource instance.
+1 more tools listed on main page
Dicom Hl7 MCP Server Tools (17)
lookup_dicom_tag
Look up any DICOM tag by number or keyword
explain_dicom_tag
Detailed tag explanation with vendor quirks and gotchas
parse_hl7_message
Parse HL7 v2.x messages into human-readable format
explain_hl7_segment
Explain segment fields, data types, and usage
lookup_hl7_table
Look up HL7 table values (Administrative Sex, Patient Class, etc.)
map_dicom_to_hl7
Map DICOM tags to HL7 v2 fields with conversion notes
map_hl7_to_fhir
Map HL7 v2 fields to FHIR R4 resources
generate_mirth_channel
Generate Mirth Connect channel configurations
validate_hl7_message
Validate HL7 messages against the standard
explain_integration_pattern
Explain healthcare integration patterns with flow diagrams