Dicom Api MCP Project MCP Server

If you already use Dicom Api MCP Project, the dicom api mcp project mcp server is the piece that lets your assistant work with it directly. Este es un servidor MCP (Model Context Protocol) que expone operaciones DICOM como herramientas para agentes de IA.

Available tools

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

• patient_id — ID del paciente
• study_date — Fecha del estudio (YYYYMMDD)
• accession_number — Número de acceso
• patient_name — Nombre del paciente
• additional_filters — Filtros adicionales
• study_instance_uid — UID del estudio (requerido)
• series_instance_uid — UID de la serie (requerido)
• fields_to_retrieve — Campos específicos a recuperar
• sop_instance_uid — UID de la instancia (opcional)
• query_studies — Busca estudios en el PACS - patient_id: ID del paciente - study_date: Fecha del estudio (YYYYMMDD) - accession_number: Número de acceso -
• query_series — Busca series dentro de un estudio - study_instance_uid: UID del estudio (requerido) - additional_filters: Filtros adicionales
• query_instances — Busca metadatos de instancias en una serie - study_instance_uid: UID del estudio (requerido) - series_instance_uid: UID de la serie (requerido) -

Credentials and setup notes

Configuration is passed through the environment: DICOM_SERVER_URL, DICOM_SERVER_BASE_URL. 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.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dicom Api MCP Project's toolset — patient_id, study_date, accession_number and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aotal; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dicom Api MCP Project's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Dicom Api MCP Project.
• 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.