Open Health Sync

io.github.soma-intelligencePublished by GitHub account soma-intelligencev0.2.0Updated Nov 5, 2026

Read-only access to self-hosted health data: samples, sleep, workouts, nutrition, daily summaries.

VerifiedSTDIODesktop onlyDatabasesLocation & Lifestyle

Overview

AI-generated overview

Read-only MCP access to a self-hosted Open Health Sync instance, letting an assistant read health samples, sleep, workouts, nutrition and daily summaries.

What you can do
  • Read health samples collected from wearables and health apps
  • Review sleep, workout and nutrition records
  • Pull daily summaries of health data
  • Query one unified format instead of per-device exports
When to use it
Useful when you already run (or plan to run) an Open Health Sync server and want an AI assistant to read your consolidated health data for review, summaries or questions, without giving it write access.
Requirements
A running Open Health Sync instance reachable over HTTPS (plain HTTP only for loopback hosts), set via OHS_MCP_URL. A user token with read scope or a tenant API key, supplied as OHS_MCP_KEY. Runs as a local process (container image, stdio transport); Docker is needed to self-host the server.
Before you install
OHS_MCP_KEY is a credential granting read access to personal health data; keep it out of logs and shared configs. Health data is sensitive, so point OHS_MCP_URL only at a server you control or trust. The hosted beta is test data only, and the project is not a medical device.

Installation

In SourceWeft

  1. Open Open Health Sync in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Sync health data in peace. Koi drawn in characters swim around the line, in an endless loop.]

Open Health Sync

One API for all your health data. Free, open source, on your own server.

[CI] [Release] [License: AGPL-3.0]

What it does

Every health app and wearable sends data in its own format. Open Health Sync collects it all and gives it back in one clean format, through one API.

  • In: Apple Health, Health Connect, Garmin, Oura, WHOOP, Fitbit, Withings, Polar, Strava, Dexcom and more.
  • Out: a REST API, FHIR R4, Open mHealth, signed webhooks, CSV and Parquet, native SDKs, and an MCP server so an AI agent can read your data.
  • Runs anywhere: one program plus Postgres, even on a Raspberry Pi. Your data stays with you.

Try it

You need Docker.

sh
git clone https://github.com/soma-intelligence/open-health-sync.git && cd open-health-synccp .env.example .envsed -i.bak "s|^OHS_ENCRYPTION_KEY=.*|OHS_ENCRYPTION_KEY=$(openssl rand -base64 32)|" .envdocker compose --env-file .env -f deploy/docker-compose.yml up -d --waitdocker compose --env-file .env -f deploy/docker-compose.yml exec ohs /ohs seed --demo

The last command loads 90 days of sample data and prints an API key and calls to try.

Or run it on a hosting platform, no server of your own:

[Deploy to Render]

Fly.io and Railway steps are in Deploy on a platform.

Next steps: API guide, self-hosting, releases.

Don't want to run a server?

Use the free hosted beta: same API, nothing to install. Test data only for now.

Learn more

Documentation · FAQ · Compare with Terra and others · Connect an AI agent · Contributing · Security

Not a medical device. Licensed under AGPL-3.0.

Source: README.md at commit cad8a65

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

2
  1. v0.2.0LatestOct 22, 2026
  2. v0.1.0Oct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts