DICOM MCP Server: Global Collaboration & Data Integrity

Mirror, manage, and master medical imaging workflows with DICOM MCP Server—your seamless gateway to global healthcare collaboration and data integrity.

Visit Repository

✨ Research And Data

4.8(108 reviews)

162 saves

75 comments

Users create an average of 13 projects per month with this tool

About DICOM MCP Server

What is DICOM MCP Server: Global Collaboration & Data Integrity?

The DICOM MCP Server is a specialized testing framework designed to facilitate DICOM protocol validation and interoperability across distributed systems. By integrating with the Model Context Protocol (MCP), it enables seamless collaboration between global healthcare institutions while maintaining data integrity through standardized node configurations and AE title management. This server acts as a central hub for verifying DICOM operations like C-ECHO, ensuring compliance with international healthcare data standards.

How to Use DICOM MCP Server: Global Collaboration & Data Integrity?

Implementation follows three core steps:
1. Environment Setup: Install UV runtime via pip install uv and verify system PATH configuration.
2. Server Deployment: Choose between traditional Python-based installation or MCP-managed deployment for automatic lifecycle management.
3. Operational Execution: Run DICOM operations through CLI commands, leveraging node configurations stored in nodes.yaml to abstract low-level network parameters.

DICOM MCP Server Features

Key Features of DICOM MCP Server: Global Collaboration & Data Integrity?

Centralized Node Management: Stores DICOM node configurations in YAML format, enabling role-based access and standardized AE title usage
Context-Aware Operations: Performs C-ECHO and other DICOM transactions using pre-configured endpoint parameters
Automated Compliance: Enforces data integrity checks through predefined protocol validation rules
Multi-Tenant Support: Facilitates secure collaboration between geographically distributed systems via role-scoped access controls

Use Cases for DICOM MCP Server: Global Collaboration & Data Integrity?

Primarily used in:
• Validation of cross-institutional PACS/RIS integration
• Pre-production testing of DICOM-enabled medical devices
• Compliance audits for HIPAA/FDA regulatory standards

DICOM MCP Server FAQ

FAQ: Troubleshooting DICOM MCP Server

Q: "Received ENOENT error during UV execution"
A: Ensure UV executable is added to system PATH and node configuration files are properly formatted. Verify nodes.yaml syntax using yamllint.

Q: "C-ECHO command returns invalid AE title"
A: Check nodes.yaml for mismatched AE title entries. Use mcp validate to audit configuration consistency across all registered nodes.

Q: "How to reset server state between tests?"
A: Execute mcp reset to purge cached configurations and restart the MCP runtime environment.

Content

DICOM MCP Server

A Model Context Protocol (MCP) server for DICOM connectivity testing.

Prerequisites

Install UV (required):

pip install uv

Make sure uv is available in your system PATH as it's required for Claude to properly execute the server.

Installation

There are two ways to set up the server:

1. Traditional Setup

Install the required dependencies:

uv pip install mcp[cli]

2. MCP Installation (Recommended)

To use this server with Claude's Model Context Protocol:

mcp install server.py

This will register the server with Claude for DICOM operations.

Running the Server

Direct Execution

uv run server.py

Through Claude

Once installed via MCP, the server will be automatically managed by Claude when needed.

The server will start on 0.0.0.0:8080 by default.

Node Configuration

The server uses a nodes.yaml file to store DICOM node configurations. This allows you to:

List all configured DICOM nodes
Perform C-ECHO operations using node names instead of explicit AE titles, IPs, and ports
Use different local AE titles for C-ECHO operations

nodes.yaml Format

nodes:
  # Example node configuration
  main_pacs:
    ae_title: DESTINATION
    ip: 192.168.1.100
    port: 104
    description: "Main hospital PACS system"

local_ae_titles:
  - name: default
    ae_title: MCP_DICOM
    description: "Default AE title for MCP DICOM server"
  
  - name: pacs_gateway
    ae_title: PACS_GATEWAY
    description: "PACS Gateway AE title"

Troubleshooting

If you encounter the "spawn uv ENOENT" error, it typically means one of the following:

UV is not installed or not in your PATH
The Python executable cannot be found by the MCP client

Solutions:

Make sure UV is properly installed and in your PATH:

which uv # Should show the path to UV
Ensure you're using a Python environment that's accessible to the system:

* If using a virtual environment, make sure it's activated
* Check that Python is in your PATH

Try running the server with explicit UV path:

/full/path/to/uv run server.py
Add more debugging by checking the stderr output in the logs

Usage

The server provides several DICOM tools that can be used through the MCP interface:

List DICOM Nodes

List all configured DICOM nodes from the nodes.yaml file:

list_dicom_nodes()

C-ECHO by Node Name

Perform a C-ECHO operation using a node name from the configuration:

dicom_cecho_by_name(node_name="main_pacs", local_ae_name="default")

Direct C-ECHO

Perform a C-ECHO operation with explicit parameters:

dicom_cecho(remote_ae_title="REMOTE_AE", ip="192.168.1.100", port=104, local_ae_title="MCP_DICOM")