Loading...
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.
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.