In-depth architectural comparison of the Dicom MCP 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
Dicom MCP
Biology, Medicine and Bioinformatics · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Dicom Hl7 MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Dicom MCP 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 Dicom MCP 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: Patient, study, series, and instance queries, Encapsulated PDF text extraction, C-MOVE transfers for studies and series.
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.
DICOM integration to query, read, and move medical images and reports from PACS and other DICOM compliant systems.
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
Dicom MCP Tools (6)
Patient, study, series, and instance queries
Encapsulated PDF text extraction
C-MOVE transfers for studies and series
DICOM node switching and listing
C-ECHO connection verification
Configurable metadata detail presets
Dicom Hl7 MCP Server Tools (17)
lookup_dicom_tag
Look up any DICOM tag by number or keyword
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 MCP 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 Dicom MCP when you need capabilities focused on biology, medicine and bioinformatics and Dicom Hl7 MCP Server when you require tools for biology, medicine and bioinformatics.