Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Securely access and manage FHIR healthcare data stored in Medplum.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.medplum.com/mcp/streamRun this in your terminal
claude mcp add --transport http medplum https://api.medplum.com/mcp/streamPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"medplum": {
"url": "https://api.medplum.com/mcp/stream"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"medplum": {
"type": "http",
"url": "https://api.medplum.com/mcp/stream"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.medplum.com/mcp/streamMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain medplum.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Medplum is a developer platform that enables flexible and rapid development of healthcare apps.
To build an application with an AI agent, start with the AI coding guide to connect Medplum's rules to your agent and plan with the decision guides.
We heartily welcome any and all contributions that match our engineering standards!
That being said, this codebase isn't your typical open-source project because it's not a library or package with a limited scope -- it's our entire product. Our Contributing documentation has all the information you need to get started.
By making a contribution to this project, you are deemed to have accepted the Developer Certificate of Origin (DCO).
All conversations and communities on Medplum are expected to follow GitHub's Community Guidelines and Acceptable Use Policies. We expect discussions on issues and pull requests to stay positive, productive, and respectful. Remember: there are real people on the other side of the screen!
If you found a technical bug on Medplum or have ideas for features we should implement, the issue tracker is the best place to share with us. (click here to open a new issue)
Did you learn how to do something using Medplum that wasn't obvious on your first try? By contributing your new knowledge to our documentation, you can help others who might have a similar use case!
Our documentation is hosted on medplum.com/docs, but it is built from Markdown files in our docs package.
For relatively small changes, you can edit files directly from your web browser on GitHub.dev without needing to clone the repository.
To keep new contributors focused on work we're ready to accept, code contributions go through an approval system: your Pull Request must be linked to an issue labeled open-to-community before we'll review it. This signals that a maintainer has explicitly invited community help on that issue. You can link a PR to an issue with a closing keyword in the PR description (e.g. Fixes #123) or via GitHub's Development panel. PRs that aren't linked to an open-to-community issue are automatically closed, but can be reopened once the link is added. Established contributors and Medplum team members are exempt from this requirement.
If you find a bug, look for an existing issue labeled open-to-community, or open a new issue and ask us to label it, before starting work on a fix.
If you want to implement a new feature, open an issue first to discuss with us how the feature might work, and to ensure it fits into our roadmap and plans for the app.
If you want to contribute but are unsure how to start, we have a "good first issue" label which is applied to newcomer-friendly issues. Take a look at the full list of good first issues and pick something you like!
Ready to get started writing code? Follow the local setup instructions and jump in! See our full contributing guide for more details on this process.
With the ground rules out of the way, let's talk about the coarse architecture of this mono repo:
Here is a list of all the big technologies we use:
medplum/
├── packages │ ├── agent # On-premise agent │ ├── app # Frontend web app │ ├── bot-layer # AWS Lambda Layer for Bots │ ├── cdk # AWS CDK infra as code │ ├── cli # Command line interface │ ├── core # Core shared library │ ├── definitions # Data definitions │ ├── docs # Documentation │ ├── examples # Example code used in documentation │ ├── fhir-router # FHIR URL router │ ├── fhirtypes # FHIR TypeScript definitions │ ├── generator # Code generator utilities │ ├── graphiql # Preconfigured GraphiQL │ ├── hl7 # HL7 client and server │ ├── mock # Mock FHIR data for testing │ ├── react # React component library │ ├── react-hooks # React hooks library │ └── server # Backend API server └── scripts # Helper bash scripts
Thanks to Chromatic for providing the visual testing platform that helps us review UI changes and catch visual regressions.
Apache 2.0