Open Health Sync

by soma-intelligenceio.github.soma-intelligence/open-health-syncv0.2.0

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

  • Runs on your machine
  • No known advisories
  • AGPL-3.0

Version checks

Not run yet – package checks are being switched on. It runs from a package on your machine, so instead of uptime we will start each new version in our sandbox.

How we check

Run it on your machine

Add to ~/.config/agenvoy/mcp.json:

{
  "servers": {
    "open-health-sync": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}

Replace YOUR_OHS_MCP_URL,YOUR_OHS_MCP_KEY with your own values.

For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Open Health Sync (`io.github.soma-intelligence/open-health-sync`)

Its page: https://plug.directory/servers/io.github.soma-intelligence/open-health-sync

It runs on the person's machine and needs Docker installed.

Ask the person for `YOUR_OHS_MCP_URL`, `YOUR_OHS_MCP_KEY` and put it in place of the placeholder; never invent a value.

Use the section for the person's client.

## Claude Desktop, Cursor, Devin Desktop, Cline, LM Studio, Gemini CLI, mcp-client-cli, oterm, TUUI, BoltAI, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Claude Desktop: claude_desktop_config.json (Settings › Developer › Edit Config)
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- mcp-client-cli: ~/.llm/config.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- TUUI: resources/assets/config/mcp.json in the installed app
- BoltAI: ~/.boltai/mcp.json
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "open-health-sync": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --env OHS_MCP_URL=YOUR_OHS_MCP_URL --env OHS_MCP_KEY=YOUR_OHS_MCP_KEY --transport stdio open-health-sync -- docker run -i --rm -e OHS_MCP_URL -e OHS_MCP_KEY ghcr.io/soma-intelligence/open-health-sync:0.2.0 mcp
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "open-health-sync": {
      "type": "stdio",
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "open-health-sync": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "open-health-sync"
    type: stdio
    command: "docker"
    args:
      - "run"
      - "-i"
      - "--rm"
      - "-e"
      - "OHS_MCP_URL"
      - "-e"
      - "OHS_MCP_KEY"
      - "ghcr.io/soma-intelligence/open-health-sync:0.2.0"
      - "mcp"
    env:
      "OHS_MCP_URL": "YOUR_OHS_MCP_URL"
      "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "open-health-sync":
    type: stdio
    name: "open-health-sync"
    enabled: true
    cmd: "docker"
    args: ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"]
    env_keys: []
    envs: { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    timeout: 300
```

## Codex

Run in a terminal:

```sh
codex mcp add open-health-sync --env OHS_MCP_URL=YOUR_OHS_MCP_URL --env OHS_MCP_KEY=YOUR_OHS_MCP_KEY -- docker run -i --rm -e OHS_MCP_URL -e OHS_MCP_KEY ghcr.io/soma-intelligence/open-health-sync:0.2.0 mcp
```

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "open-health-sync": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "open-health-sync": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "OHS_MCP_URL", "-e", "OHS_MCP_KEY", "ghcr.io/soma-intelligence/open-health-sync:0.2.0", "mcp"],
      "env": { "OHS_MCP_URL": "YOUR_OHS_MCP_URL", "OHS_MCP_KEY": "YOUR_OHS_MCP_KEY" }
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Known advisories

None known for its packages.

Checked 2026-10-28 against OSV.dev and deps.dev.

From the publisher's entry in the Official MCP Registry (the registry entry)and from Go modules. We have not checked this server yet. Report a problem