Fluxinc Dicom MCP Server

🚀 DICOM MCP Server

A Model Context Protocol (MCP) server for DICOM connectivity testing. It provides a reliable way to test DICOM connections and perform related operations.

🚀 Quick Start

Before starting the server, make sure you have completed the necessary preparations and installations.

✨ Features

• Conduct DICOM connectivity tests.
• Support two installation methods, with the MCP installation method recommended.
• Use the nodes.yaml file to store DICOM node configuration information for easy management.
• Provide multiple DICOM tools through the MCP interface.

📦 Installation

Prerequisites

1. Install UV (Required):

   pip install uv
   

   Ensure that uv is installed in your system's PATH, as it is crucial for Claude to run the server correctly.

Installation Methods

There are two ways to set up the server:

1. Traditional Installation

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 automatically register the server in Claude for DICOM operations.

💻 Usage Examples

Running the Server

Direct Execution

uv run server.py

Through Claude

Once installed via MCP, Claude will automatically manage the server as needed.

The server will run on port 0.0.0.0:8080 by default.

Node Configuration

The server uses a nodes.yaml file to store the configuration information of DICOM nodes. This allows you to:

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

nodes.yaml File 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: "AE title for PACS gateway"

Troubleshooting

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

1. UV is not installed or is not in the system PATH.
2. The Python executable cannot be found by the MCP client.

Solutions:

1. Ensure that UV is correctly installed and in the PATH:

   which uv  # Should display the path of UV
   

2. Ensure that you are using an accessible Python environment:

   • If using a virtual environment, make sure it is activated.
   • Check if Python is in the PATH.

3. Try running the server by specifying the full path of UV:

   /full/path/to/uv run server.py
   

4. Add more debugging information by checking the stderr output in the logs.

Using DICOM Tools

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

Listing DICOM Nodes

List all configured DICOM nodes in the configuration file:

list_dicom_nodes()

Performing C - ECHO by Node Name

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

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

Performing C - ECHO Directly

Perform a C - ECHO operation using explicit parameters:

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