Your data, in Claude.

Claude can reason about almost anything — except the numbers your apps keep locked away. MissingMCP hands it your real data, starting with Garmin, so you can just ask: “Did I eat enough for today’s ride?” — and get an answer that actually knows.

Connect Garmin →

Just ask

No dashboards, no exports. A real question, a real answer — from your own data.

YouI had chicken and rice for lunch. Am I on track for today’s long run?
ClaudeGarmin has you at ~2,850 kcal burned so far today, with a 90-minute run still to come (~950 kcal). Lunch was ~620 kcal — you’re running a deficit for the load ahead. Grab a carb-heavy snack before you head out.

Two sources — your Garmin and what you told Claude — connected in one answer. No single app does that.

“How did I sleep this week?” “Compare my last three long runs.” “Why was my recovery low today?”

Connectors

Beta

WHOOP

Recovery, sleep, and strain — ask why today’s recovery dipped, what your HRV is doing, or how the week’s load is trending.

Connect WHOOP →
Soon

Oura

Sleep, readiness, and heart rate from your Oura ring — ask how last night set up your day, or how readiness tracks with your training. In the works.

Soon

Apple Health

Bringing your Apple Health data into Claude is on the radar — still exploring the right way to do it, no promises yet.

Missing something?

Every connector here started as “I wish Claude could…”. Tell me which app should be next — or just get a ping when a new one lands.

How it works

Step 1

Pick a connector

Choose an app from the list and copy its server URL.

Step 2

Add it to Claude

Settings → Connectors → Add custom connector. Paste the URL and nothing else — leave the optional OAuth Client ID and Client Secret fields empty. Works on phone, desktop, and web.

Step 3

Sign in once

Claude opens a sign-in page — log in with your own account. Where the service has its own OAuth (WHOOP), you sign in there; elsewhere (Garmin) your password is used once and never stored.

Step 4

Start asking

Claude picks up the tools automatically. “How did I sleep this week?” just works.

Security & trust

You’re signing in with real credentials — here’s exactly how they’re handled.

Passwords: never stored — often never seen

Where the service offers its own OAuth (WHOOP), you sign in there and this gateway never sees a password. Where it doesn’t (Garmin), your password signs you in once and is immediately discarded. Either way, only the resulting tokens are kept — encrypted with AES-256-GCM.

Standard OAuth 2.1

Claude never sees your credentials. It gets its own revocable token, over the same OAuth + PKCE flow that banks and APIs use.

Your data passes through, nothing sticks

Your health and fitness data flows from the service to Claude only when you ask, and only to you. The gateway stores none of it — details in the privacy policy.

Open source, run by a person

MissingMCP is open source, built by Vaclav Slajs — the full source is on GitHub; audit it, or run your own. This instance is run by the operator.

No longer missing

The best possible ending for a connector: the service ships an official one. These apps now speak MCP themselves — connect them directly, no gateway needed.

Official MCP ✓

Rohlík

Rohlík now runs its own MCP server with proper OAuth sign-in. Add https://mcp.rohlik.cz/mcp as a custom connector in Claude and log in with your Rohlík account — no password stored anywhere.

Rohlík’s official guide →

🍺 Keep MissingMCP running

Everything here is free and open source — no ads, no paywall, nothing sold. It runs on a small server I pay for out of pocket. If a connector earns a spot in your routine, buy me a beer to help keep the lights on.

🍺 Buy me a beer

Give Claude the missing piece.

Your first connector is two minutes away — free, open source, and no server of your own.

Browse connectors