Healthcare interoperability for Claude — DICOM tags, HL7v2 parsing, FHIR mapping
Connect Dicom to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Healthcare interoperability for Claude — DICOM tags, HL7v2 parsing, FHIR mapping. The dicom mcp server is what makes that connection.
Built by a healthcare IT engineer with 16 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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
lookup_dicom_tag — Look up any DICOM tag by number or keywordexplain_dicom_tag — Detailed tag explanation with vendor quirks and gotchasparse_hl7_message — Parse HL7 v2.x messages into human-readable formatexplain_hl7_segment — Explain segment fields, data types, and usagelookup_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 notesmap_hl7_to_fhir — Map HL7 v2 fields to FHIR R4 resourcesgenerate_mirth_channel — Generate Mirth Connect channel configurationsvalidate_hl7_message — Validate HL7 messages against the standardexplain_integration_pattern — Explain healthcare integration patterns with flow diagramsdecode_private_tags — Decode vendor private DICOM tags (GE, Siemens, Philips, etc.)generate_sample_message — Generate realistic sample HL7 messages for testingConfiguration is passed through the environment: 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_AUTH, DICOM_HL7_DICOMWEB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Dicom's toolset — lookup_dicom_tag, explain_dicom_tag, parse_hl7_message and 11 more — is a fair guide to whether it matches your workflow. It is maintained by NyxToolsDev; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| 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.) |
| 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 |
| pacs_echo | Verify PACS connectivity (C-ECHO or DICOMweb ping) |
| pacs_query | Search for studies/series by patient, date, modality, accession |
### With Premium License
```json
{
"mcpServers": {
"dicom-hl7-assistant": {
"command": "uvx",
"args": ["dicom-hl7-mcp"],
"env": {
"DICOM_HL7_LICENSE_KEY": "your-license-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DICOM_HL7_LICENSE_KEY | Credential the server authenticates with. | Yes |
| DICOM_HL7_PACS_AE_TITLE | Configuration value read at startup. | Optional |
| DICOM_HL7_PACS_HOST | Endpoint or connection string the server talks to. | Optional |
| DICOM_HL7_PACS_PORT | Configuration value read at startup. | Optional |
| DICOM_HL7_LOCAL_AE_TITLE | Configuration value read at startup. | Optional |
| DICOM_HL7_DICOMWEB_URL | Endpoint or connection string the server talks to. | Yes |
| DICOM_HL7_DICOMWEB_AUTH | Configuration value read at startup. | Optional |
| DICOM_HL7_DICOMWEB_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.