rt-imaging-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RT_IMAGING_MCP_ROOT | Yes | Path to the root directory containing the medical image files. Required unless the --root command line argument is provided. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only access to local medical image files (DICOM, NIfTI) below one configured root directory. Output is deliberately minimal: patient identifiers, pixel data and absolute paths are never returned. Do not try to retrieve identifying information. Research use only; not for clinical decisions.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dicom_scan_directoryA | Inventory DICOM series below a directory (path relative to the root). Returns opaque series ids, modality, instance counts and image size. Study and series UIDs are never returned. Set opaque_paths=True to omit all file and directory names. Only DICOM Part 10 files (with the DICM preamble) are detected. |
| dicom_get_metadataA | Read allowlisted technical attributes of one DICOM file (path relative to the root). Use dicom_list_allowed_tags to see which keywords are allowed. Requesting any other keyword fails. Patient identifiers and pixel data are never returned. |
| dicom_list_allowed_tagsA | List the DICOM attribute keywords that dicom_get_metadata can currently return. |
| nifti_infoA | Return shape, voxel size, data type, units and orientation of a NIfTI file. Only structural header fields are returned. Free-text header fields and the image data are never read into the output. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: one reads single-file DICOM metadata, one scans directories, one lists allowed DICOM tags, and one inspects NIfTI headers. The helper/listing tool is explicitly framed as supporting the metadata tool, so boundaries remain clear.
Three tools follow a consistent dicom_verb_noun pattern, while nifti_info follows a separate modality prefix and uses a noun-style name rather than a verb. The pattern is still highly readable and mostly predictable across the set.
Four tools is well-scoped for a narrow, read-only imaging metadata server. Each tool earns its place by covering a specific inspection need without adding redundant operations.
The DICOM side covers directory inventory, allowed-tag discovery, and metadata retrieval, and the NIfTI side covers header inspection. Minor gaps exist, such as no equivalent inventory operation for NIfTI files, but the core read-only metadata purpose is covered.