What is the key difference between Dicom Hl7 MCP Server and Tebra?

Dicom Hl7 MCP Server belongs to the Biology, Medicine and Bioinformatics category with local stdio execution, while Tebra belongs to the Biology, Medicine and Bioinformatics category with local stdio execution.

How do I install Dicom Hl7 MCP Server or Tebra 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 Hl7 MCP Server and Tebra free or paid?

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

Which MCP server has more tools and community activity?

Dicom Hl7 MCP Server lists 17 tools with 2 views and 4 GitHub stars. Tebra lists 47 tools with 1 views and 1 GitHub stars.

Can I use both Dicom Hl7 MCP Server and Tebra 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 Hl7 MCP Server vs Tebra

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

Biology, Medicine and Bioinformatics · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Tebra

Biology, Medicine and Bioinformatics · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Verdict Summary: Choose Dicom Hl7 MCP Server if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Tebra 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 Dicom Hl7 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 (Freemium).
You have access to required keys: DICOM_HL7_LICENSE_KEY, DICOM_HL7_PACS_AE_TITLE, DICOM_HL7_PACS_HOST, DICOM_HL7_PACS_PORT, DICOM_HL7_LOCAL_AE_TITLE, DICOM_HL7_DICOMWEB_URL, DICOM_HL7_DICOMWEB_TOKEN, DICOM_HL7_DICOMWEB_USERNAME.
Primary tools included: lookup_dicom_tag, explain_dicom_tag, parse_hl7_message.

Explore Dicom Hl7 MCP Server Details

Choose Tebra when:

You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Feature & Specification Comparison

Specification	Dicom Hl7 MCP Server NyxToolsDev Biology, Medicine and Bioinformatics	Tebra Biology, Medicine and Bioinformatics
Summary	The only MCP server bridging DICOM, HL7v2, and FHIR in one package. Cross-standard mapping, Mirth Connect channel generation, vendor private tag decoding (GE, Siemens, Philips), and integration pattern knowledge. Built by a 19-year healthcare IT veteran. pip install dicom-hl7-mcp	MCP server for Tebra/Kareo practice management — patients, billing, scheduling, FHIR (45 tools)
Category & Scope	Biology, Medicine and Bioinformatics

Tools & Capabilities Breakdown

Dicom Hl7 MCP Server Tools (17)

lookup_dicom_tag

Look up any DICOM tag by number or keyword

explain_dicom_tag

Detailed tag explanation with vendor quirks and gotchas

parse_hl7_message

Parse HL7 v2.x messages into human-readable format

explain_hl7_segment

Explain segment fields, data types, and usage

lookup_hl7_table

Look up HL7 table values (Administrative Sex, Patient Class, etc.)

map_dicom_to_hl7

Map DICOM tags to HL7 v2 fields with conversion notes

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 Hl7 MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "nyxtoolsdev-dicom-hl7-mcp-server": {
      "command": "uvx",
      "args": [
        "dicom-hl7-mcp"
      ],
      "env": {
        "DICOM_HL7_LICENSE_KEY": "YOUR_DICOM_HL7_LICENSE_KEY_HERE",
        "DICOM_HL7_PACS_AE_TITLE": "YOUR_DICOM_HL7_PACS_AE_TITLE_HERE",
        "DICOM_HL7_PACS_HOST": "YOUR_DICOM_HL7_PACS_HOST_HERE",
        "DICOM_HL7_PACS_PORT": "YOUR_DICOM_HL7_PACS_PORT_HERE",
        "DICOM_HL7_LOCAL_AE_TITLE": "YOUR_DICOM_HL7_LOCAL_AE_TITLE_HERE",
        "DICOM_HL7_DICOMWEB_URL": "YOUR_DICOM_HL7_DICOMWEB_URL_HERE",
        "DICOM_HL7_DICOMWEB_TOKEN": "YOUR_DICOM_HL7_DICOMWEB_TOKEN_HERE",
        "DICOM_HL7_DICOMWEB_USERNAME": "YOUR_DICOM_HL7_DICOMWEB_USERNAME_HERE"
      }
    }
  }
}

Tebra Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tebra": {
      "command": "npx",
      "args": [
        "-y",
        "tebra-mcp-server"
      ]
    }
  }
}

Frequently Asked Questions

Dicom Hl7 MCP Server is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Tebra belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Dicom Hl7 MCP Server when you need capabilities focused on biology, medicine and bioinformatics and Tebra when you require tools for biology, medicine and bioinformatics.

More alternatives to Dicom Hl7 MCP Server More alternatives to Tebra Biology, Medicine and Bioinformatics category hub