Dicom MCP Server

🚀 DICOM MCP Server

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

🚀 Quick Start

The DICOM MCP Server is designed for DICOM connection testing. It offers a convenient way to manage DICOM operations and provides useful DICOM tools through the MCP interface.

✨ Features

• Allows for two installation methods: traditional and MCP installation.
• Automatically managed by Claude after MCP installation.
• Uses nodes.yaml for DICOM node configuration, enabling easy management of DICOM nodes.
• Provides multiple DICOM tools, such as listing nodes and performing C - ECHO operations.

📦 Installation

Prerequisites

1. Install UV (Required):

   pip install uv
   

   Ensure that uv is installed in your system's PATH, as it is necessary for Claude to execute 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 register the server with Claude for DICOM operations.

💻 Usage Examples

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 runs on 0.0.0.0:8080 by default.

Node Configuration

The server uses the nodes.yaml file to store the configuration 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 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"

DICOM Tools

List DICOM Nodes

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

list_dicom_nodes()

Perform C - ECHO by Node Name

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

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

Direct C - ECHO Execution

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")

🔧 Technical Details

Troubleshooting

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

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 added to the PATH:

   which uv  # Should display the path of UV
   

2. Ensure that you are using a Python environment accessible to the system:
   • If using a virtual environment, make sure it is activated.
   • Check if Python is in your PATH.
3. Try running the server using the full path of UV:

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

4. Perform more debugging by checking the stderr output in the error log.