In-depth architectural comparison of the Fhir MCP Server and Dicomweb MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Fhir MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 65/100 (Great) | Auth: API Key required
Dicomweb MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 59/100 (Good) | Auth: other
Verdict Summary: Choose Fhir MCP Server if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Dicomweb MCP Server if your workspace requires Biology, Medicine and Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Fhir MCP Server when:
You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: FHIR_SERVER_BASE_URL, FHIR_SERVER_CLIENT_ID, FHIR_SERVER_CLIENT_SECRET, FHIR_SERVER_SCOPES, FHIR_SERVER_DISABLE_AUTHORIZATION, FHIR_MCP_HOST, FHIR_MCP_PORT.
Model Context Protocol server for Fast Healthcare Interoperability Resources (FHIR) APIs. Provides seamless integration with FHIR servers, enabling AI assistants to search, retrieve, create, update, and analyze clinical healthcare data with SMART-on-FHIR authentication support.
A DICOMweb MCP server that exposes a DICOMweb-compliant DICOM archive to AI assistants, enabling search of studies, series and instances, metadata inspection, structured report reading, encapsulated PDF text extraction, and frame rendering.
Category & Scope
Tools & Capabilities Breakdown
Fhir MCP Server Tools (13)
get_capabilities
Retrieves metadata about a specified FHIR resource type, including its supported search parameters and custom operations.
type
The FHIR resource type name (e.g., "Patient", "Observation", "Encounter")
search
Executes a standard FHIR search interaction on a given resource type, returning a bundle or list of matching resources.
searchParam
A mapping of FHIR search parameter names to their desired values (e.g., {"family":"Simpson","birthdate":"1956-05-12"}).
response_filter_fhirpaths
(Optional) An array of FHIRPath expressions (e.g., `["Patient.name", "Patient.birthDate", "Bundle.link.where(relation='next').url"]`) to apply to the resources in the response bundle.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Fhir MCP Server is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Dicomweb MCP Server belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Fhir MCP Server when you need capabilities focused on biology, medicine and bioinformatics and Dicomweb MCP Server when you require tools for biology, medicine and bioinformatics.
Performs a FHIR "read" interaction to retrieve a single resource instance by its type and resource ID, optionally refining the response with search parameters or custom operations.
id
The logical ID of a specific FHIR resource instance.
operation
The name of a custom FHIR operation or extended query defined for the resource (e.g., "$everything").
create
Executes a FHIR "create" interaction to persist a new resource of the specified type.
payload
A JSON object representing the full FHIR resource body to be created.
update
Performs a FHIR "update" interaction by replacing an existing resource instance's content with the provided payload.
delete
Execute a FHIR "delete" interaction on a specific resource instance.
+1 more tools listed on main page
Dicomweb MCP Server Tools (9)
find-studies
Searches DICOM studies on the configured DICOMweb server. Results are sorted by study date, newest first.
find-series
Searches DICOM series within a single study. Results are sorted by series date, newest first.
find-instances
Searches DICOM instances within a single series. Results are sorted by Instance Number ascending.
find-encapsulated-pdf-reports
Finds all Encapsulated PDF instances in a study by looking for DOC-modality series and filtering by the Encapsulated PDF SOP Class UID (`1.2.840.10008.5.1.4.1.1.104.1`).
get-encapsulated-pdf-report-text
Retrieves an Encapsulated PDF DICOM instance and extracts its text content.
find-structured-reports
Finds all Structured Report (SR) instances in a study by looking for SR-modality series and filtering by known SR SOP Class UIDs.
get-structured-report-text
Retrieves a Structured Report instance and converts it to human-readable text.
get-instance-metadata
Retrieves and formats all DICOM attributes of a single instance as human-readable text. Does not retrieve pixel data.
render-instance-frame
Renders a specific frame from a DICOM instance and returns it as an inline image (JPEG or PNG).