Dicom Hl7 MCP Server vs Dicomweb MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Dicom Hl7 MCP Server vs Dicomweb MCP Server
In-depth architectural comparison of the Dicom Hl7 MCP Server and Dicomweb 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
Dicom Hl7 MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Dicomweb MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 59/100 (Good) | Auth: other
Verdict Summary: Choose Dicom Hl7 MCP Server if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Dicomweb 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 Dicom Hl7 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 (Freemium).
You have access to required keys: DICOM_HL7_LICENSE_KEY, DICOM_HL7_PACS_AE_TITLE, DICOM_HL7_PACS_HOST, DICOM_HL7_PACS_PORT, DICOM_HL7_LOCAL_AE_TITLE, DICOM_HL7_DICOMWEB_URL, DICOM_HL7_DICOMWEB_TOKEN, DICOM_HL7_DICOMWEB_USERNAME.
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
A DICOMweb MCP server that exposes a DICOMweb-compliant DICOM archive to AI assistants, enabling search of studies, series and instances, metadata inspection, structured report reading, encapsulated PDF text extraction, and frame rendering.
Tools & Capabilities Breakdown
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
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).
Dicom Hl7 MCP Server is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Dicomweb MCP Server belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Dicom Hl7 MCP Server when you need capabilities focused on biology, medicine and bioinformatics and Dicomweb MCP Server when you require tools for biology, medicine and bioinformatics.
Generate realistic sample HL7 messages for testing
+5 more tools listed on main page
Dicomweb MCP Server Tools (9)
find-studies
Searches DICOM studies on the configured DICOMweb server. Results are sorted by study date, newest first.
find-series
Searches DICOM series within a single study. Results are sorted by series date, newest first.
find-instances
Searches DICOM instances within a single series. Results are sorted by Instance Number ascending.
find-encapsulated-pdf-reports
Finds all Encapsulated PDF instances in a study by looking for DOC-modality series and filtering by the Encapsulated PDF SOP Class UID (`1.2.840.10008.5.1.4.1.1.104.1`).
get-encapsulated-pdf-report-text
Retrieves an Encapsulated PDF DICOM instance and extracts its text content.
find-structured-reports
Finds all Structured Report (SR) instances in a study by looking for SR-modality series and filtering by known SR SOP Class UIDs.
get-structured-report-text
Retrieves a Structured Report instance and converts it to human-readable text.
get-instance-metadata
Retrieves and formats all DICOM attributes of a single instance as human-readable text. Does not retrieve pixel data.
render-instance-frame
Renders a specific frame from a DICOM instance and returns it as an inline image (JPEG or PNG).