ghurt — Your agent can't read your sleep score.

How it works

Connect once. Your agent handles the rest.

Connect your wearable

Whoop and Oura use OAuth. Garmin requires a one-time login to establish access. We never store the password — only the session data needed to keep the connection alive.

Whoop Oura Garmin
02
Add ghurt to your agent

One command adds ghurt to Claude Code, Cursor, OpenClaw, or any MCP-compatible agent. One endpoint covers all your connected devices.
Claude Code
```
claude mcp add --scope user ghurt -- \
  npx mcp-remote@latest "https://ghurt.org/v1/mcp?key=YOUR_API_KEY"
```
Use your data for real decisions

Ask for summaries, comparisons, calendar changes, dashboards, and patterns. Your agent can now reason from your actual data instead of guessing.

What it looks like in practice

Less manual checking. More useful answers.

▶ Adjust my calendar today based on recovery, sleep, and yesterday's training load

> [ghurt] Queried sleep, HRV, recovery, strain, and today's calendar context

Sleep was 5h 52m, HRV is below baseline, and yesterday's strain was high. I’d move your hardest deep-work block from 9am to early afternoon, keep training easy, and leave more recovery time between meetings.

▶ Summarize what changed this week across sleep, recovery, and workload

> [ghurt] Queried sleep duration, HRV trend, recovery scores, workouts, and travel days for the last 7 days

Recovery dropped after Tuesday’s travel day. Sleep duration stayed below baseline for three nights, resting HR trended up, and workout strain remained high. The main pattern is accumulated load plus worse sleep, not a single bad session.

█

Example conversation — actual responses depend on your agent and model. ghurt provides the data layer.

Built for people who want health data to actually do something.

Real things your agent can now help with

Use it for decisions, summaries, comparisons, and dashboards.

Adjust my calendar today based on recovery and sleep
Rebuild this week's training around my recovery since Tuesday
Summarize what changed this week across sleep, HRV, and strain
Compare my Garmin and Oura recovery signals this week
What patterns usually show up before my recovery drops?
Build a 30-day dashboard of sleep, HRV, resting HR, and workouts

Why ghurt feels better than wiring it yourself

The point isn’t just access. It’s cleaner access that stays useful.

Maintained connections

Garmin, Oura, and Whoop in one place — without turning your weekend project into a maintenance project.

Agent-ready tools and instructions

Custom tools and structured instructions help your agent interpret the data correctly instead of fumbling provider-specific metrics.

Compact outputs

Cleaner responses mean fewer wasted tokens and less prompt bloat when your agent works with wearable data.

Simple pricing

Start free. Upgrade when you need more.

Free

30 uses per calendar month

Maintained connection across Garmin, Oura, and Whoop
30 health data queries per calendar month
Works with Claude and Cursor
Also: OpenClaw + any MCP client
No health data persisted on our servers

Start free

Pro

$ 10 /month

Unlimited uses

Everything in Free, plus unlimited queries
Sleep, recovery, HRV, strain, and workouts — fetched when your agent asks
Works with Claude and Cursor
Also: OpenClaw + any MCP client
No health data persisted on our servers
Custom tools and instructions built for agent use
Revoke access or delete your account at any time

Get Pro — $10/month

No surprises.

Minimal surface area, by design

We fetch your data when your agent asks. We don’t keep a copy.

Whoop and Oura — standard OAuth

No passwords involved. You authorize through each provider’s own login flow.

Garmin — password used once, then discarded

Garmin doesn’t offer OAuth for this use case. We use your credentials once to establish session access, then discard the password. Only the session data needed to keep the connection alive is stored.

Health data is not stored

Your HRV, sleep scores, recovery data, and workouts don’t live on our servers. They pass through on demand when your agent requests them.

Full revocation, anytime

Disconnect any device or delete your account whenever you want. We’ll purge stored account and connection data within 24 hours and confirm by email.

Frequently asked questions

: You can. The problem is that wearable APIs change without notice, and Garmin auth in particular breaks regularly. What starts as an afternoon project becomes a maintenance burden. ghurt keeps the connections working and structures the outputs so agents can actually use the data. $10/month is cheaper than debugging Garmin auth at midnight before a race.
: Currently: Whoop, Oura Ring, and Garmin devices that sync through Garmin Connect.
: ghurt fetches your data on demand when your agent requests it. There’s no continuously synced copy on our servers — data is pulled fresh each time.
: No. We don’t store your health metrics. We store only the minimum session and account data needed to authenticate requests and keep your endpoint working.
: Yes. Use the Delete my data link in the footer, or email us directly. We’ll purge stored account and connection data within 24 hours and confirm by email.
: Any MCP-compatible agent works. The most common are Claude Code, Cursor, and OpenClaw. If your agent supports MCP servers over HTTP, it works with ghurt.
: MCP (Model Context Protocol) is an open standard that lets AI agents connect to external tools and data sources. ghurt exposes your wearable data through that standard, so any compatible agent can request it on demand.

Your agent can't read your sleep score.