5 #interoperability MCP Servers & Clients
Every MCP server and client below is tagged #interoperability — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to interoperability tools.
All
Healsens FHIR MCP
healsens
Dicom/hl7/fhir Interoperability Mcp Server
NyxToolsDev
Built by a healthcare IT engineer with 19 years of PACS/RIS/integration experience. Bridges DICOM, HL7v2, and FHIR — maps between standards, decodes vendor private tags (GE, Siemens, Philips), generates Mirth Connect channels, and explains integration patterns. 12 tools covering
HL7 Tools — Parser, Validator, FHIR R4 Converter
easysolutions906
Parse, explain, validate, generate, diff, and convert HL7 v2 messages. Supports versions 2.3-2.8 with 600+ CARISTIX field definitions. Bidirectional HL7 v2 to FHIR R4 conversion. 9 tools.
Aidress
Aidress-ai
Aidress is the coordination layer for autonomous AI agents. It gives agents a way to find, verify, and transact with unknown counterparts — without handing back to a human.
Mirth Connect MCP Server — 18 Tools for Channel Development, Debugging, and CI/CD
easysolutions906
The first and most comprehensive MCP server for Mirth Connect. 18 tools: parse channels, generate Rhino-compatible code, lint for anti-patterns, debug errors, diff channels between environments, extract SQL for DBA review, map channel dependencies, generate CI/CD deploy scripts,
Frequently asked questions
What is a #interoperability MCP server?
- An MCP server tagged #interoperability implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access interoperability-related tools, data, or APIs.
How many #interoperability MCP servers and clients are there?
- mcp.so currently lists 5 MCP servers and clients tagged #interoperability.
How do I install a #interoperability MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.