DICOM Connectivity
About
Integrates with DICOM systems to provide connectivity testing and diagnostics for medical imaging workflows, enabling node listing, C-ECHO operations, and configuration management.
Details
- Author
- fluxinc
- Repository
- fluxinc/dicom-mcp-server
- GitHub stars
- 2
- Downloads
- 331
- License
- GNU Lesser General Public License v2.1
- Categories
- Productivity, Design, Developer Tools, AI, Infrastructure, Frontend, Other
Jump to
- DICOM C‑ECHO operations via node names or explicit parameters
- Configuration stored in a YAML file (nodes.yaml)
- Two installation methods: traditional or MCP‑install for Claude
- Multiple local AE titles can be defined and selected per operation
- Listing all configured DICOM nodes from the YAML file
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
DICOM ConnectivityCommand (node, npx, python, etc.)npxArguments-
Argument 1
-y -
Argument 2
@highlight/mcp-server
Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
-
Argument 1
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
There are two ways to set up the server:
Install the required dependencies:
uv pip install mcp[cli]
To use this server with Claude's Model Context Protocol:
mcp install server.py
This will register the server with Claude for DICOM operations.
The server uses a nodes.yaml file to store DICOM node configurations. 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
list_dicom_nodes
List all configured DICOM nodes from the nodes.yaml file.
dicom_cecho_by_name
Perform a C-ECHO operation using a node name from the configuration. Parameters: node_name (string), local_ae_name (string)
dicom_cecho
Perform a C-ECHO operation with explicit parameters. Parameters: remote_ae_title (string), ip (string), port (int), local_ae_title (string)
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"dicom connectivity": {
"env": {},
"args": [
"-y",
"@highlight/mcp-server"
],
"command": "npx"
}
}
}Linux
{
"env": [],
"args": [
"-y",
"@highlight/mcp-server"
],
"command": "npx"
}Macos
{
"env": [],
"args": [
"-y",
"@highlight/mcp-server"
],
"command": "npx"
}Windows
{
"env": [],
"args": [
"/c",
"npx",
"-y",
"@highlight/mcp-server"
],
"command": "cmd"
}DICOM MCP Server
A Model Context Protocol (MCP) server for DICOM connectivity testing.
Prerequisites
1. 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:
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
```yaml
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
