Maintainer of this skill?
Open source health data aggregator and self-hosted Terra alternative. One API for wearable data from Apple Health, Health Connect, Oura, WHOOP, Withings, Fitbit, Dexcom and more: REST, FHIR R4, Open mHealth, webhooks, CSV/Parquet and a read-only MCP server. One Go binary plus Postgres. AGPL-3.0.
# Add to your Claude Code skills
git clone https://github.com/soma-intelligence/open-health-syncGuides for using mcp servers skills like open-health-sync.
See how open-health-sync compares with popular alternatives.
open-health-sync is an open-source mcp servers skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by soma-intelligence. Open source health data aggregator and self-hosted Terra alternative. One API for wearable data from Apple Health, Health Connect, Oura, WHOOP, Withings, Fitbit, Dexcom and more: REST, FHIR R4, Open mHealth, webhooks, CSV/Parquet and a read-only MCP server. One Go binary plus Postgres. AGPL-3.0. It has 50 GitHub stars.
open-health-sync's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/soma-intelligence/open-health-sync" and add it to your Claude Code skills directory (see the Installation section above).
open-health-sync is primarily written in Go. It is open-source under soma-intelligence on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other MCP Servers skills you can browse and compare side by side. Open the MCP Servers category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh open-health-sync against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Apple Health, Withings, Oura, WHOOP, Fitbit, Health Connect, Dexcom, OMRON and ten more. One clean model out, over REST, FHIR R4 and a read-only MCP server for AI agents. Free, one Go binary plus Postgres, runs on a Raspberry Pi. An open source, self-hosted alternative to hosted wearable APIs such as Terra.
docker pull ghcr.io/soma-intelligence/open-health-sync:0.2.0
Rather not run a server? The hosted beta is the same API with nothing to operate: a key in a minute, demo data on the first call. Get started for free → · Sign in to the developer portal · ▶ Watch the 75-second tour
Quickstart · Hosted beta · Compare · Roadmap · Use cases · Why · Features · How it works · MCP · FAQ
If it saves you one more parser, a ⭐ star helps other developers find it. Questions and ideas: Discussions.
v0.2.0, early preview. APIs, configuration and schema may change in any 0.x release.
The quickstart, recorded on v0.1.0 with synthetic data: start the stack, load 90 days from six devices, then read one day of the merged view, one heart rate reading as REST, FHIR R4 and Open mHealth, and the MCP tools. Nothing is mocked; the tape renders it again.
Open Health Sync (ohs) is a self-hosted ingestion and normalization layer for health data. It
pulls from providers, accepts uploads from phones, stores each payload verbatim, maps it to one
canonical model with one set of units, and serves it over a REST API and a read-only MCP server.
It is not a dashboard or a coaching app, and it is not a medical device or clinical software.
Run it yourself, or let us run it for you in the hosted beta.
🔌 Eighteen sources, one model
Every provider maps into the same records, with one unit per quantity (UCUM, LOINC). Heart rate
is bpm, whatever the source called it. All eighteen ship in v0.2.0.
⚡ Always current
Provider webhooks trigger a pull of just what changed. A backstop pull catches anything lost,
and /freshness says how up to date each source is.
🧾 Nothing thrown away Every payload is kept verbatim on disk or S3. Fix a mapper, re-process a user from the raw files. Re-sent uploads are de-duplicated.
🤖 Ready for AI agents A read-only MCP server: a person points their own agent at their own data, with a token that can only read.
🏥 Standards out An OpenAPI 3.1 REST API, plus FHIR R4 Observations checked against the official HL7 validator.
🔒 Yours, and erasable
Self-hosted, no call home. DELETE /v1/users/{id} is a hard delete of rows and raw files.
Provider deletions are honored too.
The same server, run for you. The hosted beta is Open Health Sync without a Postgres, a raw store or workers to operate: you sign in, create a key and read data on your first call.