Open Health Sync MCP Server

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

Local serverstdio

What is the Open Health Sync MCP Server?

Open Health Sync is an MCP integration. Read-only access to self-hosted health data: samples, sleep, workouts, nutrition, daily summaries.

Packages and local setup

The published oci package is ghcr.io/soma-intelligence/open-health-sync:0.1.0. Its declared MCP transport is stdio.

The package declares OHS_MCP_URL (required): Base URL of your Open Health Sync instance. Must be https unless the host is loopback (inside a container, loopback is the container itself).; OHS_MCP_KEY (required): A user token with the read scope (ohs_ut_...) or a tenant API key (ohs_sk_...)..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related sports & fitness MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
OHS_MCP_URLBase URL of your Open Health Sync instance. Must be https unless the host is loopback (inside a container, loopback is the container itself).Yes
OHS_MCP_KEYA user token with the read scope (ohs_ut_...) or a tenant API key (ohs_sk_...).Yes