Healthcare interoperability for Claude — DICOM tags, HL7v2 parsing, FHIR mapping
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-nyxtoolsdev-dicom-hl7-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The only MCP server that bridges DICOM, HL7v2, and FHIR in one package — with optional PACS connectivity.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in health
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
MCP server for the ClinicalTrials.gov v2 API. Search trials, retrieve study details and results, and match patients to eligible trials.
Manage your Hevy workouts, routines, folders, and exercise templates. Create and update sessions faster, organize plans, and search exercises to build workouts quickly. Stay synced with changes so your training log is always up to date.
MCP server for Oura Ring API v2 (sleep, activity, readiness, heart rate, workouts).
MCP Security Weekly
Get CVE alerts and security updates for io.github.NyxToolsDev/dicom-hl7-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The only MCP server that bridges DICOM, HL7v2, and FHIR in one package — with optional PACS connectivity.
Built by a healthcare IT engineer with 19 years of PACS, RIS, and integration experience. This isn't a wrapper around a FHIR API or a DICOM tag dictionary — it's the interoperability knowledge that takes years on the job to build, plus the ability to connect to real PACS systems.
| Capability | This Server | DICOM-only servers | FHIR-only servers |
|---|---|---|---|
| DICOM tag lookup + vendor quirks | Yes | Yes | No |
| HL7v2 message parsing | Yes | No | No |
| FHIR R4 resource mapping | Yes | No | Yes |
| DICOM ↔ HL7v2 mapping | Yes | No | No |
| HL7v2 → FHIR conversion | Yes | No | No |
| Mirth Connect channel generation | Yes | No | No |
| PACS connectivity (C-FIND/C-MOVE) | Yes | Some | No |
| DICOMweb (QIDO-RS/WADO-RS) | Yes | No | No |
| Query PACS + auto-map to HL7/FHIR | Yes | No | No |
| Vendor private tag decoding (GE, Siemens, Philips) | Yes | Some | No |
| Integration pattern knowledge (IHE SWF, ADT flows) | Yes | No | No |
| Tool | What It Does |
|---|---|
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.) |
| Tool | What It Does |
|---|---|
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 |
decode_private_tags | Decode vendor private DICOM tags (GE, Siemens, Philips, etc.) |
generate_sample_message | Generate realistic sample HL7 messages for testing |
| Tool | What It Does |
|---|---|
pacs_echo | Verify PACS connectivity (C-ECHO or DICOMweb ping) |
pacs_query | Search for studies/series by patient, date, modality, accession |
pacs_get_metadata | Retrieve detailed study/series metadata from PACS |
pacs_retrieve | C-MOVE images to a destination AE title |
pacs_study_summary | Query a study + auto-map through DICOM→HL7→FHIR with generated ORM |
Reference tools only (no PACS connectivity):
pip install dicom-hl7-mcp
With PACS connectivity (adds pynetdicom + httpx):
pip install dicom-hl7-mcp[pacs]
Add to your Claude Desktop config:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"dicom-hl7-assistant": {
"command": "uvx",
"args": ["dicom-hl7-mcp"]
}
}
}
{
"mcpServers": {
"dicom-hl7-assistant": {
"command": "uvx",
"args": ["dicom-hl7-mcp"],
"env": {
"DICOM_HL7_LICENSE_KEY": "your-license-key-here"
}
}
}
}
Connect to a PACS using C-FIND/C-MOVE/C-ECHO:
{
... [View full README on GitHub](https://github.com/NyxToolsDev/dicom-hl7-mcp-server#readme)