DICOM/HL7/FHIR Interoperability MCP Server

The only MCP server that bridges DICOM, HL7v2, and FHIR in one package - with optional PACS connectivity. Its 17 documented tools cover hl7, pacs, dicom, explain. It runs locally over stdio via the published package.

People who work with hl7, pacs and dicom and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-07-29 · ★ 4 · #54 OF 71 MAINTAINED SCIENCE & HEALTH · VERIFIED 2026-09-18

MIT · Python servers · how we verify → /methodology

01 · Install DICOM/HL7/FHIR Interoperability MCP Server

before you install - you'll need

Set 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 before connecting.

Claude Code

claude mcp add nyxtoolsdev-dicom-hl7-mcp-server -- uvx dicom-hl7-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "nyxtoolsdev-dicom-hl7-mcp-server": {
      "command": "uvx",
      "args": [
        "dicom-hl7-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

pypi package dicom-hl7-mcp - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.NyxToolsDev is GitHub-verified and matches the repo owner

03 · What DICOM/HL7/FHIR Interoperability MCP Server can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can generate realistic sample HL7 messages for testing, search for studies/series by patient, date, modality, accession, retrieve detailed study/series metadata from PACS, and query a study + auto-map through DICOM→HL7→FHIR with generated ORM.

Capability map

Tools grouped from the project's README - what DICOM/HL7/FHIR Interoperability MCP Server lets an agent do.

Pacs

5 tools - e.g. Verify PACS connectivity (C-ECHO or DICOMweb ping); Search for studies/series by patient, date, modality, accession; Retrieve detailed study/series metadata from PACS

pacs_echo · pacs_query · pacs_get_metadata · pacs_retrieve · pacs_study_summary

Explain

3 tools - e.g. Detailed tag explanation with vendor quirks and gotchas; Explain segment fields, data types, and usage; Explain healthcare integration patterns with flow diagrams

explain_dicom_tag · explain_hl7_segment · explain_integration_pattern

read & search

2 tools - e.g. Look up any DICOM tag by number or keyword; Look up HL7 table values (Administrative Sex, Patient Class, etc.)

lookup_dicom_tag · lookup_hl7_table

Map

2 tools - e.g. Map DICOM tags to HL7 v2 fields with conversion notes; Map HL7 v2 fields to FHIR R4 resources

map_dicom_to_hl7 · map_hl7_to_fhir

Generate

2 tools - e.g. Generate Mirth Connect channel configurations; Generate realistic sample HL7 messages for testing

generate_mirth_channel · generate_sample_message

Parse

1 tool - e.g. Parse HL7 v2.x messages into human-readable format

parse_hl7_message

Validate

1 tool - e.g. Validate HL7 messages against the standard

validate_hl7_message

Decode

1 tool - e.g. Decode vendor private DICOM tags (GE, Siemens, Philips, etc.)

decode_private_tags

04 · Who maintains DICOM/HL7/FHIR Interoperability MCP Server

DICOM/HL7/FHIR Interoperability MCP Server is maintained by nyxtoolsdev. We track 4 MCP servers from nyxtoolsdev - 4 actively maintained, 6 combined GitHub stars, oldest repo from Mar 2026. Full record: all servers from nyxtoolsdev.

  1. claude-memory-manager Cross-session memory for Claude Code - context capture, semantic search, recall ★ 2

05 · Facts

category
science & health - ranked #54 of 71 actively-maintained science & health servers as of 2026-09-18.
registry
io.github.NyxToolsDev/dicom-hl7-mcp-server (active, first published 2026-03-25 · 2 versions)
packages
pypi:dicom-hl7-mcp

06 · DICOM/HL7/FHIR Interoperability MCP Server FAQ

Is DICOM/HL7/FHIR Interoperability MCP Server still maintained?

Yes - as of 2026-09-18, its last commit was 2026-07-29. We re-verify nightly.

What can DICOM/HL7/FHIR Interoperability MCP Server do?

With this server connected, an agent can generate realistic sample HL7 messages for testing, search for studies/series by patient, date, modality, accession, retrieve detailed study/series metadata from PACS, and query a study + auto-map through DICOM→HL7→FHIR with generated ORM.

How do I install DICOM/HL7/FHIR Interoperability MCP Server?

Run `uvx dicom-hl7-mcp`. The README documents 8 environment variables (DICOM_HL7_LICENSE_KEY, DICOM_HL7_PACS_AE_TITLE, DICOM_HL7_PACS_HOST…) to set first. Set 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 before connecting. You can also paste the ready-made client config above.

Does DICOM/HL7/FHIR Interoperability MCP Server run locally?

Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to DICOM/HL7/FHIR Interoperability MCP Server