DICOMweb MCP Server
Let Claude Code or Cursor query and retrieve studies from a PACS or DICOMweb archive while you build health-tech or imaging workflows.
Overview
DICOMweb MCP Server is a MCP server for the Build phase that exposes a DICOMweb archive to AI assistants through QIDO-RS and WADO-RS.
What is this MCP server?
- Exposes QIDO-RS search and WADO-RS retrieval against any DICOMweb base URL
- stdio MCP install via npx with DICOMWEB_HOST as the single required endpoint
- Supports basic or bearer auth via DICOMWEB_AUTH, DICOMWEB_USER, and DICOMWEB_PASS
- Targets AI assistants that need structured access to DICOM studies without custom PACS SDK code
- Version 0.0.4 on npm as dicomweb-mcp-server
- npm package dicomweb-mcp-server at version 0.0.4
- stdio transport with required env DICOMWEB_HOST
- Auth modes: basic, bearer, or unauthenticated
Community signal: 2 GitHub stars.
What problem does it solve?
Agents cannot safely query or fetch DICOM studies from your archive without you hand-rolling DICOMweb HTTP clients and auth for every session.
Who is it for?
Indie builders integrating Claude or Cursor into DICOMweb-backed apps, research tooling, or internal imaging workflows where the archive URL is already known.
Skip if: Teams without a DICOMweb endpoint, non-clinical SaaS, or anyone who needs full diagnostic viewers rather than agent-driven API access.
What do I get? / Deliverables
After registration, your agent can search and retrieve imaging data from your configured DICOMweb host using standard RS endpoints and your chosen auth mode.
- MCP tools for DICOM study query and instance retrieval
- Agent-readable access aligned with DICOMweb RS standards
Recommended MCP Servers
Journey fit
Canonical shelf is Build because wiring an agent to QIDO-RS/WADO-RS is an integration task during product development, not day-two ops tuning. Integrations subphase fits MCP bridges to external clinical imaging APIs rather than frontend UI or generic backend CRUD.
How it compares
DICOMweb protocol bridge via MCP, not a PACS UI, DICOM parser library, or HIPAA compliance package by itself.
Common Questions / FAQ
Who is DICOMweb MCP Server for?
Solo and small teams building health or imaging software who already use DICOMweb and want agents to query and fetch studies through MCP.
When should I use DICOMweb MCP Server?
Use it during Build when you need repeatable agent access to study search and WADO retrieval against a configured DICOMweb base URL.
How do I add DICOMweb MCP Server to my agent?
Add the stdio MCP entry with npx dicomweb-mcp-server, set DICOMWEB_HOST to your archive base URL, and configure DICOMWEB_AUTH plus credentials if required.