Skip to content
Last updated

The JondaX MCP server lets AI assistants talk to the JondaX health data transformation engine directly. Point an assistant at a lab report or a device photo and it can upload the file, track processing, and pull back clean, structured, coded results — all through natural language, without you writing any integration code.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI applications connect to external tools and data sources. Think of it as a bridge: it gives assistants like Claude, Cursor, and Antigravity a safe, standard way to call real services and act on your behalf.

The JondaX MCP server is the JondaX side of that bridge. It exposes the JondaX processing modules as MCP tools, so an assistant can upload files and retrieve results as part of a conversation. The server handles authentication and API calls for you — the assistant just focuses on the task.

The JondaX MCP server is a local connector: your AI tool launches it on demand and talks to it over standard input/output. Any tool that can run a local (stdio) MCP server can use it.

Supported AI clients

The JondaX MCP server runs as a local process that your AI tool starts for you. The clients below are known to support local (stdio) MCP servers, so they can connect to JondaX using the Setup guide. The MCP ecosystem is growing fast — if your tool can launch a local MCP server, it can use JondaX even if it isn't listed here.

Desktop apps

AI clientNotes
Claude DesktopAnthropic desktop app
ChatGPT DesktopLocal MCP server support

IDEs & code editors

AI clientNotes
KiroAgentic IDE
CursorAI-first code editor
Google AntigravityAgentic IDE
WindsurfAI code editor
VS Code (GitHub Copilot)Via MCP support in Copilot
JetBrains AI AssistantIntelliJ, PyCharm, etc.
ZedMultiplayer code editor
ClineVS Code extension
ContinueOpen-source IDE assistant

Command-line tools

AI clientNotes
Claude CodeAnthropic CLI
Gemini CLIGoogle CLI
OpenAI Codex CLIOpenAI CLI
Amazon Q Developer CLIAWS CLI

What the JondaX MCP server does

JondaX exposes both processing modules and its retrieval endpoints as MCP tools:

ToolTypeWhat it does
upload_pathology_scanAsyncUploads a lab report or pathology document (PDF, image, and more). JondaX de-identifies, extracts, normalises, and translates the data, then returns an uploadId for tracking.
upload_medical_deviceSyncUploads an image of a device reading (pulse oximeter, blood pressure monitor, glucometer, etc.) and returns the extracted values immediately.
get_upload_statusQueryChecks the processing and callback delivery status for an uploadId.
get_extracted_resultsQueryRetrieves the structured extracted results for a completed upload (JSON, FHIR JSON, FHIR XML, HL7, CSV, Parquet).

For full parameters and examples, see the Tools reference. To get connected, follow the Setup guide.

Common use cases

Conversational document processing

Hand a file to your assistant and let it run the pipeline end to end:

  • "Upload this lab report <filepath> and give me the uploadId — I'll check back later."
  • "Extract the readings from this glucometer photo <filepath> ."
  • "Pull the result for upload <uploadId>."

Batch triage and monitoring

  • "Check the status of these three uploads <uploadIds> and let me know which have finished."

Building AI features into your product

  • Add natural-language document intake to a health app.
  • Let support agents process a patient file without leaving the chat.
  • Wire JondaX extraction into an internal AI workflow or agent.

How it works

How the JondaX MCP server works

The assistant acts as the MCP client and JondaX runs the MCP server. A typical pathology run: the assistant calls upload_pathology_scan and gets back an uploadId, JondaX processes the file asynchronously, and the assistant retrieves the structured output with get_extracted_results.

Supported output formats

  • FHIR: FHIR JSON, FHIR XML (Observation, DiagnosticReport)
  • HL7: HL7 v2
  • Standard data: JSON, CSV, Parquet
  • Terminology & coding: LOINC, standard clinical units, normalised ranges

Compliance

The JondaX MCP server runs against the same JondaX engine as the API, built for healthcare data. HIPAA · GDPR · PDPA · ISO 27001