simple-dicom-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@simple-dicom-mcpfind studies for patient ID 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Repo credit: https://github.com/ChristianHinge/dicom-mcp
Run it
Minimal config (
configuration.yaml):
nodes:
orthanc:
host: "localhost"
port: 4242
ae_title: "ORTHANC"
description: "Default Local Orthanc DICOM server"
aliases: ["local", "dev-orthanc"]
radiant:
host: "localhost"
port: 11112
ae_title: "RADIANT"
description: "Radiant Viewer Dicom Node"
aliases: ["viewer"]
current_node: "orthanc"
calling_aets:
default:
ae_title: "MCPSCU"
description: "Default calling AE"
calling_aet: "default"
query_root: "study"
allow_remote_hosts: false
network:
acse_timeout: 10
dimse_timeout: 30
network_timeout: 30
assoc_timeout: 10
max_pdu: 16384
retry:
max_attempts: 2
backoff_seconds: 1.0
backoff_multiplier: 2.0
backoff_max_seconds: 5.0
Start server (dev):
uv run --with-editable '.' -m dicom_mcp configuration.yamlIf uv caches old code: add
--no-cacheor--reinstall-package simple-dicom-mcp.
Claude Desktop (working JSON)
{
"mcpServers": {
"DicomMCP": {
"command": "C:\\Windows\\System32\\wsl.exe",
"args": [
"--distribution",
"Ubuntu",
"--",
"bash",
"-lc",
"cd '/mnt/c/Users/paulo/Python Projects/simple-dicom-mcp' && uv run --with-editable '.' python -m dicom_mcp '/mnt/c/Users/paulo/Python Projects/simple-dicom-mcp/configuration.yaml'"
]
}
},
"globalShortcut": "",
"preferences": {
"menuBarEnabled": false
}
}WSL tips
Enable mirrored networking so
localhostworks for both Windows and WSL.Use
--with-editable '.'so your code changes are seen live.
Tools you can call
Connection:
list_dicom_nodes,switch_dicom_node,verify_connectionRegistry:
get_manifestQuery:
query_patients,query_studies,query_series,query_instances,get_attribute_presets
Query tools return structured status metadata:
{
"success": true,
"results": [],
"dicom_statuses": [],
"warnings": [],
"error": null
}Examples
Find studies in a date range:
query_studies(study_date="20230101-20231231")Filter studies by patient attributes:
query_studies(patient_id="12345678", patient_sex="O", patient_birth_date="19700101")Troubleshooting
If uv doesnβt reflect code changes, add
--no-cacheor--reinstall-package simple-dicom-mcp.On WSL/Windows, enable mirrored networking so
localhostworks across Windows and WSL.
License & credit
MIT license (see LICENSE)
Based on: https://github.com/ChristianHinge/dicom-mcp
The simple-dicom-mcp server enables AI assistants to query and read data on DICOM servers (PACS, VNA, etc.).
π€ Contributing guide β’ π Report bug β’ π Support β’ π Security
β¨ Core Capabilities
simple-dicom-mcp provides tools to:
π Query Metadata: Search for patients, studies, series, and instances using various criteria.
βοΈ Utilities: Manage connections and understand query options.
π Quick Start
π₯ Installation
Install using uv:
uv tool install simple-dicom-mcpOr by cloning the repository:
# Clone and set up development environment
git clone https://github.com/ThalesMMS/simple-dicom-mcp
cd simple-dicom-mcp
# Create and activate virtual environment
uv venv
source .venv/bin/activate
# Install with dev dependencies
uv pip install -e ".[dev]"βοΈ Configuration
simple-dicom-mcp requires a YAML configuration file (config.yaml or similar) defining DICOM nodes and calling AE titles. Adapt the configuration or keep as is for compatibility with the sample ORTHANC Server.
nodes:
main:
host: "localhost"
port: 4242
ae_title: "ORTHANC"
description: "Local Orthanc DICOM server"
aliases: ["local", "dev-orthanc"]
current_node: "main"
calling_aets:
default:
ae_title: "MCPSCU"
description: "Default calling AE"
calling_aet: "default"
query_root: "study"
allow_remote_hosts: false
network:
acse_timeout: 10
dimse_timeout: 30
network_timeout: 30
assoc_timeout: 10
max_pdu: 16384
retry:
max_attempts: 2
backoff_seconds: 1.0
backoff_multiplier: 2.0
backoff_max_seconds: 5.0
Notes:
calling_aetcan be a name, alias, or AE title defined incalling_aets.query_rootacceptsstudyorpatient.allow_remote_hostsdefaults tofalseand blocks non-loopback DICOM hosts unless you explicitly opt in.
Simple DICOM-MCP is not meant for clinical use, and should not be connected with live hospital databases or databases with patient-sensitive data. Doing so could lead to both loss of patient data, and leakage of patient data onto the internet. If you intentionally need a remote PACS or VNA, setallow_remote_hosts: true only after reviewing the risk and using a private, trusted environment.
(Optional) Sample ORTHANC server
If you don't have a DICOM server available, you can run a local ORTHANC server using Docker:
Clone the repository and install test dependencies:
uv pip install -e ".[dev]"Start Orthanc and run tests:
cd tests
docker compose up -d
cd ..
uv run pytest -m integrationUI at http://localhost:8042
π MCP Integration
Add to your client configuration (e.g. claude_desktop_config.json):
{
"mcpServers": {
"dicom": {
"command": "uv",
"args": ["tool","simple-dicom-mcp", "/path/to/your_config.yaml"]
}
}
}For development:
{
"mcpServers": {
"simple-dicom-mcp": {
"command": "uv",
"args": [
"--directory",
"path/to/cloned/simple-dicom-mcp",
"run",
"simple-dicom-mcp",
"/path/to/your_config.yaml"
]
}
}
}π οΈ Tools Overview
simple-dicom-mcp provides five categories of tools for interaction with DICOM servers and DICOM data.
π Query Metadata
query_patients: Search for patients based on criteria like ID or birth date.query_studies: Find studies using patient ID, date, modality, description, accession number, or Study UID.query_series: Locate series within a specific study using modality, series number/description, or Series UID.query_instances: Find individual instances (images/objects) within a series using instance number or SOP Instance UID
βοΈ Utilities
list_dicom_nodes: Show the currently active DICOM node, calling AE title, and list all configured nodes.switch_dicom_node: Change the active DICOM node for subsequent operations.verify_connection: Test the DICOM network connection to the currently active node using C-ECHO.get_attribute_presets: List the available attribute presets (none, custom) for metadata query results.get_manifest: Return the MCP tool contract manifest (required/optional tool versions).
Example interaction
The tools can be chained together to answer complex questions:
π€ Community health
Read
CONTRIBUTING.mdbefore opening a pull request.Use the issue forms for bugs and focused feature ideas.
Follow
SECURITY.mdfor vulnerability reporting.Use
SUPPORT.mdfor setup/help guidance.Do not post PHI, real DICOM studies, or live PACS credentials in issues or PRs.
π Contributing
Running Tests
Unit tests run without Orthanc; integration tests require a running Orthanc DICOM server. You can use Docker:
# Navigate to the directory containing docker-compose.yml (e.g., tests/)
cd tests
docker compose up -dRun unit tests using uv:
# From the project root directory
uv run pytest -m "not integration"Run integration tests using uv:
# From the project root directory
uv run pytest -m integrationStop the Orthanc container:
cd tests
docker compose downDebugging
Use the MCP Inspector for debugging the server communication:
npx @modelcontextprotocol/inspector uv run simple-dicom-mcp /path/to/your_config.yaml --transport stdioLogging
Set LOG_LEVEL to control verbosity (e.g., DEBUG, INFO, WARNING):
LOG_LEVEL=DEBUG uv run simple-dicom-mcp /path/to/your_config.yaml --transport stdioLinting, formatting, type checking
uv run ruff check .
uv run ruff format .
uv run pyrightPre-commit
uv run pre-commit install
uv run pre-commit run --all-filesπ Acknowledgments
Built using pynetdicom
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ThalesMMS/simple-dicom-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server