K01 MCP Server
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., "@K01 MCP ServerGenerate 50 synthetic patients with Type 2 diabetes aged 40-65"
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.
K01 MCP Server
Generate and query clinically realistic synthetic health data directly from your AI workflow.
K01's MCP server gives AI agents and LLM-powered tools access to privacy-preserving synthetic health data generation. Generate FHIR-compliant patient cohorts, query structured EHR data, and compare across FHIR versions — all with built-in differential privacy. No real patient data is involved at any point.
This repository contains documentation and configuration for the K01 MCP server. The server implementation is proprietary and runs on K01 infrastructure.
Available Tools
Tool | Description | Key Parameters |
| Generate synthetic patient cohorts with demographic and clinical constraints |
|
| Search a virtual patient database with advanced healthcare filters |
|
| Retrieve a complete patient record with medication and condition summaries |
|
| Get detailed medication records with ATC codes and therapeutic indications |
|
| Retrieve patient conditions with ICD-10 codes and localized names |
|
| Compare the same patient data across FHIR R4 and R5 |
|
All tools support both FHIR R4 and R5. See docs/tools.md for full parameter documentation.
Related MCP server: FhirMCP
Quick Start
Claude Desktop
Add to your Claude Desktop configuration (Settings > MCP Servers):
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Cursor
Add to your Cursor MCP configuration (.cursor/mcp.json):
{
"mcpServers": {
"k01": {
"url": "https://mcp.k01.is/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Restart the application after adding the configuration. The K01 tools will appear in the tool list.
Authentication
The K01 MCP server uses Bearer token authentication. Include your API key in the Authorization header.
To get an API key, contact K01 at k01.is. Self-service key provisioning is coming soon.
See docs/authentication.md for details.
Examples
Generate a diabetic cohort
"Generate 100 patients aged 40-65 with Type 2 diabetes"
The generate_synthetic_cohort tool creates a FHIR Bundle with Patient, Condition, MedicationStatement, Procedure, and Observation resources:
generate_synthetic_cohort(count=100, age_min=40, age_max=65, condition="E11.9", seed=42)Search for complex patients
"Find patients with 3+ medications and chronic conditions"
search_patients(numberOfMedicinesFrom=3, conditionTypes="chronic", _count=20)Compare FHIR versions
"How do this patient's medications look in R4 vs R5?"
compare_fhir_versions(patient_id="0101302989", resource_type="Medication")See docs/examples.md for more workflows.
Privacy and Security
All data generated by K01 is fully synthetic. No real patient data is used, stored, or referenced at any point in the pipeline.
Differential privacy — noise injection with configurable epsilon values ensures generated distributions cannot be reverse-engineered to identify real individuals
No training on real data — the generation models are built from published clinical statistics and pharmacological references, not patient records
FHIR-compliant output — all resources conform to HL7 FHIR R4/R5 specifications, making them safe drop-in replacements for real data in development and testing
Deterministic seeding — use seeds for reproducible results without persisting any patient data server-side
Links
License
This repository (documentation, configuration, and examples) is licensed under MIT. The K01 server implementation is proprietary.
This server cannot be deployed
Maintenance
Related MCP Connectors
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
131Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
US healthcare data for AI agents: CMS, FDA adverse events, CDC, NPPES NPI. Keyless, real samples.
Privacy-safe synthetic financial data for LatAm fintech, AI agents, testing and ML.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.1399MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.MIT
- AlicenseAqualityCmaintenanceProvides seamless integration with FHIR APIs, enabling AI/LLM tools to search, retrieve, and analyze clinical healthcare data with support for SMART-on-FHIR authentication and multiple transport protocols.7116 PyPI136Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI applications to securely search and manage healthcare data from FHIR R4-compliant servers with built-in safety validation for AI-generated clinical observations, preventing recording of physiologically impossible values.9 npm48 PyPIMIT