Chaining a study query into extract_pdf_text_from_dicom is what makes this more than a browser — findings in a prior report become text the model can answer from. move_series then lets you route a study to a processing node and query the result back. Treat it as a development tool: the authors are explicit that it should not touch live patient data.
A server for DICOM networks — PACS, VNA and similar. It runs the standard queries against a configured node, pulls text out of reports stored as encapsulated PDFs, and sends series or studies on to other nodes.
- Patients, studies, series and individual instances searched on the usual criteria — name, ID, birth date, date, modality, description, accession number and UIDs (query_patients, query_studies, query_series, query_instances)
- The text of a clinical report that lives inside a DICOM instance as an encapsulated PDF (extract_pdf_text_from_dicom)
- A series or a whole study sent to another configured node over C-MOVE, an image-analysis endpoint for example (move_series, move_study)
- The configured nodes listed, and the active one switched without restarting (list_dicom_nodes, switch_dicom_node)
- A C-ECHO against the active node, so you learn the association works before you query (verify_connection)
- The levels of metadata detail available for query results — minimal, standard, extended (get_attribute_presets)
A YAML file naming your DICOM nodes and the calling AE title, and a reachable DICOM server; the project ships a sample Orthanc setup for trying it without one. Python, installed as a tool with uv. The authors state it is not meant for clinical use and should not be connected to live hospital databases or patient-sensitive data.
One command — uv tool install dicom-mcp