Loading...
The dicom-mcp server allows AI assistants to interact with DICOM servers for querying, reading reports, and moving medical imaging data.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The dicom-mcp server allows AI assistants to interact with DICOM servers for querying, reading reports, and moving medical imaging data.
The dicom-mcp server is relatively safe for querying and reading DICOM data within a controlled environment. However, the ability to move data to other DICOM nodes introduces a moderate risk, especially if those nodes are not properly secured. It is crucial to configure the server with appropriate network security measures and avoid connecting it to live, unprotected hospital databases.
Performance depends on the network connection to the DICOM server and the size of the data being transferred. Optimize queries and data transfer operations for efficiency.
No direct cost, but consider the cost of network bandwidth and storage associated with moving DICOM data.
npx @modelcontextprotocol/inspector uv run dicom-mcp /path/to/your_config.yaml --transport stdio{
"mcpServers": {
"dicom": {
"command": "uvx",
"args": ["dicom-mcp", "/path/to/your_config.yaml"]
}
}
}query_patientsSearch for patients based on specified criteria.
Read-only operation, no data modification.
query_studiesFind studies based on patient ID, date, or other criteria.
Read-only operation, no data modification.
query_seriesLocate series within a study based on modality or description.
Read-only operation, no data modification.
query_instancesFind individual instances within a series.
Read-only operation, no data modification.
extract_pdf_text_from_dicomRetrieve and extract text from a PDF encapsulated in a DICOM instance.
Read-only operation, no data modification.
move_seriesSend a specific DICOM series to another configured DICOM node.
Involves data transfer, potential for exposure if destination is compromised.
move_studySend an entire DICOM study to another configured DICOM node.
Involves data transfer, potential for exposure if destination is compromised.
list_dicom_nodesShow the active DICOM node and list all configured nodes.
Read-only operation, no data modification.
switch_dicom_nodeChange the active DICOM node for subsequent operations.
Configuration change, but does not directly affect data.
verify_connectionTest the DICOM network connection to the active node.
Read-only operation, no data modification.
get_attribute_presetsList the available levels of detail for metadata query results.
Read-only operation, no data modification.
None
local
The dicom-mcp server is relatively safe for querying and reading DICOM data within a controlled environment. However, the ability to move data to other DICOM nodes introduces a moderate risk, especially if those nodes are not properly secured. It is crucial to configure the server with appropriate network security measures and avoid connecting it to live, unprotected hospital databases.
Autonomy is limited by the configured DICOM nodes and the permissions associated with the calling AE title. Exercise caution when granting autonomy to tools that move data.
Production Tip
Implement robust monitoring and logging to track data movement and identify potential issues.
dicom-mcp itself is not HIPAA compliant out-of-the-box. You must implement appropriate security measures and follow HIPAA guidelines when using it with protected health information.
You need to modify the `config.yaml` file with the correct host, port, and AE title for your PACS server.
Yes, as long as you configure a DICOM node that points to the cloud-based service and ensure secure data transfer.
The tools will likely return an error or timeout. Implement error handling in your client application to manage such scenarios.
Use network firewalls, restrict access to the configuration file, and monitor data transfer activity.
No, dicom-mcp uses traditional DICOM C-MOVE for data transfer, not DICOMweb.
No, dicom-mcp primarily focuses on querying, reading, and moving data. It does not provide tools for modifying DICOM metadata.