JondaX MCP Server
OfficialJondaX MCP Server connects AI assistants to Jonda Health's health-data transformation engine to extract, normalise, and return structured clinical data from lab reports and medical device images.
upload_pathology_scan— Upload a pathology/lab report image (JPG, PNG) or PDF for AI OCR and biomarker extraction; returns anuploadId(async).upload_medical_device— Upload a medical device image (pulse oximeter, BP monitor, glucometer, thermometer) to instantly extract digital readings (sync).get_upload_status— Check an upload's processing status (uploaded,processing,completed,failed) plus webhook delivery status.get_extracted_results— Retrieve structured results (biomarkers, values, reference ranges) asjson,fhir_json,fhir_xml,hl7,csv, orparquet; returns HTTP 202 while still processing.Standards support — FHIR (JSON/XML), HL7 v2, JSON/CSV/Parquet, LOINC coding, unit conversion, and de-identification, with HIPAA/GDPR/PDPA/ISO 27001 compliance.
Note: the README also documents a list_uploads query tool, which is not present in the provided server schema.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JondaX MCP Server Upload this pathology report PDF and extract the results as FHIR JSON."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JondaX Model Context Protocol (MCP) Server
Official Model Context Protocol (MCP) server for JondaX by Jonda Health. Connect AI assistants (Antigravity, Claude Desktop, Cursor, Zed, Cline) directly to the JondaX Health Data Transformation Engine.
JondaX extracts data from clinical files — PDFs, images, HL7, FHIR — normalises it, and returns clean, structured, coded output in the format your system needs.
Capabilities & MCP Tools
JondaX provides two core processing modules and retrieval tools:
Tool Name | Type | Description |
| Async | Uploads a pathology report or lab document (PDF, JPG, PNG, JSON, CSV, Parquet and etc). JondaX de-identifies, extracts, normalises, translates, and returns an |
| Sync | Uploads an image of a medical device reading (pulse oximeter, blood pressure monitor, glucometer, etc.) and extracts readings instantly. |
| Query | Checks processing status ( |
| Query | Lists your recent uploads (newest first) with |
| Query | Retrieves structured extracted results (JSON, FHIR JSON, FHIR XML, HL7, CSV, Parquet). Retained for 30 days. Returns HTTP 202 if still in progress. |
Related MCP server: document-intelligence-server
Configuration
Get your API key from the Integration section in the JondaX Client Portal. https://app.jondax.eu
Environment Variable | Required | Default | Description |
| Yes | — | Your JondaX API token ( |
| No |
| JondaX API Base URL |
Quickstart Setup in AI Tools
1. In Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"jondax": {
"command": "npx",
"args": ["-y", "@jondax/mcp-server"],
"env": {
"JONDAX_API_KEY": "YOUR_JONDAX_API_KEY",
"JONDAX_BASE_URL": "https://app.jondax.eu"
}
}
}
}2. In Cursor / Antigravity (mcp_config.json)
{
"mcpServers": {
"jondax": {
"command": "npx",
"args": ["-y", "@jondax/mcp-server"],
"env": {
"JONDAX_API_KEY": "YOUR_JONDAX_API_KEY",
"JONDAX_BASE_URL": "https://app.jondax.eu"
}
}
}
}How It Works
┌──────────────┐ upload_pathology_scan ┌─────────────────────────────┐
│ ├───────────────────────────────►│ JondaX Transformation Engine│
│ AI Agent │ │ • De-identifies & Extracts │
│ (Antigravity │◄───────────────────────────────┤ • Maps Medical Terminology │
│ / Claude) │ Returns uploadId │ • Converts Units & Codes │
│ │ └──────────────┬──────────────┘
│ │ get_extracted_results │
│ ├───────────────────────────────────────────────┘
│ │◄───────────────────────────────
│ │ Returns Structured Results
└──────────────┘ (JSON, FHIR, HL7, CSV, etc.)Supported Output Formats & Standards
FHIR: FHIR JSON, FHIR XML (Observation, DiagnosticReport)
HL7: HL7 v2
Standard Data: JSON, CSV, Parquet
Terminology & Coding: LOINC, standard clinical units & normalized ranges
Compliance & Security
JondaX is built specifically for healthcare data:
HIPAA · GDPR · PDPA · ISO 27001
Local Development
If contributing or building from source:
git clone https://github.com/JondaHealthTech/jondax-mcp-server.git
cd jondax-mcp-server
npm install
npm run buildDocumentation & Links
API Docs: jondax.redocly.app
Product: jonda.health/product/jondax
Client Portal: app.jondax.eu
License
MIT © Jonda Health
Available Tools
4 toolsget_extracted_resultsA
Retrieve the extracted structured results (biomarkers, test values, reference ranges) for a completed document. Defaults to your account configured format (JSON, FHIR_JSON, HL7, CSV). Returns HTTP 202 Accepted message if still in progress.
Inputs: uploadId (required), format.
get_upload_statusA
Check the processing status of an uploaded document using its uploadId. Returns whether the document is uploaded, processing, completed, or failed, along with webhook callback delivery status.
Inputs: uploadId (required).
upload_medical_deviceA
Upload a medical device scan image (pulse oximeter, blood pressure monitor, glucose meter, thermometer) to extract digital readings instantly.
Inputs: filePath (required).
upload_pathology_scanA
Upload a pathology/blood test image (JPG, PNG) or PDF document to JondaX for AI OCR and biomarker extraction. Returns an uploadId for tracking.
Inputs: filePath (required), isDemo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The two upload tools are distinguished by document type (pathology/blood test vs medical device), and the two retrieval tools are clearly separated by status vs results. There is minor potential confusion because both upload tools trigger the same OCR/extraction pipeline, but descriptions are clear enough.
All tool names follow a consistent verb_noun pattern: upload_* for ingestion and get_* for retrieval. The naming is predictable and easy to navigate.
Four tools is well-scoped for the server's purpose: upload two categories of medical documents, check status, and retrieve results. Each tool earns its place with no unnecessary redundancy.
The core workflow of upload → status → results is fully covered. Minor gaps exist around error details or listing past uploads, but agents can successfully complete the primary extraction workflow without dead ends.
Maintenance
Related MCP Connectors
Turn documents into structured, AI-ready data by parsing, enriching, chunking, and embedding.
Upload once. Find, use and share across your AI workflows.
Document conversion and OCR for AI agents: PDF, Office docs, images to text.
Convert PDF, Word, Excel and scanned documents to Markdown, tables and RAG chunks. OCR.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.MIT
- AlicenseNot gradedqualityDmaintenanceEnables intelligent document processing by extracting text, classifying document types, and generating structured summaries from PDFs and images using vision LLMs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.2MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with clinical patient records using tools for document ingestion, structured conversion, patient profiling, record listing, search, and secure Q&A over patient documentation.-