DICOMweb MCP Server

Connect DICOMweb to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server exposing a DICOMweb DICOM archive to AI assistants via QIDO-RS and WADO-RS. The dicomweb mcp server is what makes that connection.

What the server does

[NPM version][npm-version-image]][npm-url] [NPM downloads][npm-downloads-image]][npm-url] [build][build-image]][build-url] [MIT License][license-image]][license-url] [dicomweb-mcp-server MCP server][glama-score-image]][glama-score-url]

Installation

dicomweb-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Cursor — Add to .cursor/mcp.json in your project root, or to the global ~/.cursor/mcp.json:

Credentials and setup notes

Configuration is passed through the environment: DICOMWEB_HOST, DICOMWEB_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 20 or later - A running DICOMweb server supporting QIDO-RS and WADO-RS (e.g. [orthanc][orthanc-url]) The following endpoints must be supported by the DICOMweb server: | Endpoint | Service | Used by | |---|---|---| | GET /studies | QIDO-RS | Search studies | | GET /studies/{study}/series | QIDO-RS | Search series | | GET /studies/{study}/series/{series}/instances | QIDO-RS | Search

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. DICOMweb's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by PantelisGeorgiadis; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.