dicom-agent-mcp
Related Servers
Alternatives to dicom-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to query and read data on DICOM servers (PACS, VNA, etc.).91MIT
- FlicenseNot gradedqualityDmaintenanceExposes DICOM operations as tools for AI agents to interact with medical imaging systems and PACS. It enables searching for studies and series, querying instance metadata, and retrieving pixel data from DICOM entities.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and analyze medical imaging metadata from DICOM servers, including patient information, studies, series, and instances, as well as extract text from encapsulated PDF documents.105MIT
- AlicenseNot gradedqualityBmaintenanceEnables standardized PACS-AI integration through the Model Context Protocol, providing medical imaging workflows with DICOMweb transport, hierarchical PHI de-identification, and AI model orchestration.Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server that exposes a DICOMweb-compliant DICOM archive to AI assistants. It lets any MCP-capable client search studies, series and instances, inspect metadata, read Structured and Encapsulated PDF Reports, and render image frames — all through natural language.9106 npm4MIT
TDQS
Scored across 16 tools
Most tools target clearly distinct DICOM operations or local resources. The only potential overlap is among retrieve, move, store, and transfer, but their descriptions distinguish DIMSE/DICOMweb and cache-based workflows well enough.
The set is mostly snake_case and follows a predictable verb_noun pattern for local and analytical operations. The single-verb network tools (echo, search, retrieve, move, store, transfer) are standard DICOM terms, so the deviation is minor and readable.
At 16 tools it is slightly above the typical 3-15 range, but the DICOM domain justifies the breadth: network operations, local cache inspection, rendering, measurement, geometry checks, and de-identification are all represented. Each tool appears to earn its place.
The surface covers the core DICOM lifecycle: node discovery, connectivity, query/retrieve, move/store/transfer, local metadata, rendering, measurement, geometry validation, and de-identification. Minor gaps like local cache cleanup or more granular de-identification configuration are not blocking for likely agent workflows.