What Liftosaur data reaches Claude
Liftosaur is a direct strength-workout source, which means the assistant can reason over set-level training history rather than a generic workout shell. Supported imports can include exercises, warmup sets, completed sets, reps, weight, RPE, and available program context.
Wellness Project reads Liftosaur in the background and also supports Sync Now. It does not create, edit, or delete Liftosaur workouts. When the same workout also arrives through Apple Health or Health Connect, the direct Liftosaur copy is treated as the richer source so the session is not double-counted.
Claude does not receive a bulk wearable export. It asks Wellness Project for the supported rows needed for the question, through the authorized remote MCP connection with sign-in authorization.
How to connect Liftosaur to Claude
Your setup screen may look different.
AI assistants change their settings and navigation frequently. Menu names and steps can vary by web, desktop, or mobile client, device and operating system, plan, account type, version, and staged rollout. Treat the instructions on this page as a current guide and look for the equivalent Apps, Connectors, Plugins, or MCP controls if your version differs.
Create a Liftosaur API key
Liftosaur limits API access to Premium. In Liftosaur Settings → API Keys, create a personal API key.
Connect Liftosaur in Wellness Project
Open Settings → Devices → Liftosaur, paste the API key, and sync. Wellness Project reads the workout history directly from Liftosaur.
Check a recent workout
Confirm exercises, completed sets, reps, weight, RPE, and any expected program context before asking the assistant to analyze progression.
Add Wellness Project as a Claude connector
In claude.ai, open Settings → Connectors, add https://wellnessproject.ai/api/mcp as a custom remote MCP connection, then sign in and authorize your Wellness Project account.
Ask Claude about your real history
Start with a bounded date range and a concrete question. For example: "Which exercises show the clearest progression in working weight over the last eight weeks?" The assistant can then request the relevant Wellness Project rows instead of reasoning from a screenshot or one-off export.
What to ask Claude once Liftosaur is connected
The useful prompts compare your own history over time. These examples are shaped around the data this source actually sends to Wellness Project.
- Which exercises show the clearest progression in working weight over the last eight weeks?
- Compare my weekly set volume across the major lifts and flag stalled movements.
- Which sessions had the highest RPE at a similar load, and has that changed over time?
Limits of the Liftosaur → Wellness Project → Claude path
The Liftosaur integration is read-only and requires Liftosaur Premium for API access.
Liftosaur does not provide a deletion signal. If you delete a workout in Liftosaur, the imported Wellness Project copy can remain until reconciliation catches it; do not assume remote deletion is instantaneous.
Claude is reading an authorized Wellness Project MCP connection, not a native Liftosaur integration supplied by Claude's developer.
Connect Liftosaur, then ask Claude.
Sync the supported history into Wellness Project, authorize Claude, and ask questions against your real trend instead of exporting files or pasting screenshots.
