What is the key difference between Dicom MCP and MCP Server Qdrant?

Dicom MCP belongs to the Databases category with local stdio execution, while MCP Server Qdrant belongs to the Databases category with local stdio execution.

How do I install Dicom MCP or MCP Server Qdrant in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Dicom MCP and MCP Server Qdrant free or paid?

Dicom MCP operates under a Free / Open Source model (No auth required). MCP Server Qdrant operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Dicom MCP lists 6 tools with 4 views and 99 GitHub stars. MCP Server Qdrant lists 4 tools with 3 views and 1,526 GitHub stars.

Can I use both Dicom MCP and MCP Server Qdrant together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Dicom MCP vs MCP Server Qdrant

In-depth architectural comparison of the Dicom MCP and MCP Server Qdrant 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

Dicom MCP

Databases · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

MCP Server Qdrant

Databases · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Dicom MCP if you need specialized Databases tools running via a local process. Choose MCP Server Qdrant if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Dicom MCP when:

You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Patient, study, series, and instance queries, Encapsulated PDF text extraction, C-MOVE transfers for studies and series.

Explore Dicom MCP Details

Choose MCP Server Qdrant when:

You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: QDRANT_URL, QDRANT_API_KEY, QDRANT_LOCAL_PATH, COLLECTION_NAME, EMBEDDING_PROVIDER, EMBEDDING_MODEL, QDRANT_SEARCH_LIMIT, QDRANT_READ_ONLY.
Primary tools included: .

Feature & Specification Comparison

Specification	Dicom MCP ChristianHinge Databases	MCP Server Qdrant qdrant VerifiedDatabases
Summary	DICOM integration to query, read, and move medical images and reports from PACS and other DICOM compliant systems.	An official Qdrant Model Context Protocol (MCP) server implementation
Category & Scope

Tools & Capabilities Breakdown

Dicom MCP Tools (6)

Patient, study, series, and instance queries

Encapsulated PDF text extraction

C-MOVE transfers for studies and series

DICOM node switching and listing

C-ECHO connection verification

Configurable metadata detail presets

MCP Server Qdrant Tools (4)

information

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).

Dicom MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "christianhinge-dicom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

MCP Server Qdrant Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "qdrant-mcp-server-qdrant": {
      "command": "uvx",
      "args": [
        "When"
      ],
      "env": {
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE",
        "QDRANT_API_KEY": "YOUR_QDRANT_API_KEY_HERE",
        "QDRANT_LOCAL_PATH": "YOUR_QDRANT_LOCAL_PATH_HERE",
        "COLLECTION_NAME": "YOUR_COLLECTION_NAME_HERE",
        "EMBEDDING_PROVIDER": "YOUR_EMBEDDING_PROVIDER_HERE",
        "EMBEDDING_MODEL": "YOUR_EMBEDDING_MODEL_HERE",
        "QDRANT_SEARCH_LIMIT": "YOUR_QDRANT_SEARCH_LIMIT_HERE",
        "QDRANT_READ_ONLY": "YOUR_QDRANT_READ_ONLY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Dicom MCP is categorized under Databases and uses a local stdio subprocess. In contrast, MCP Server Qdrant belongs to Databases using local stdio subprocess. Select Dicom MCP when you need capabilities focused on databases and MCP Server Qdrant when you require tools for databases.

More alternatives to Dicom MCP More alternatives to MCP Server Qdrant Databases category hub