Local-first MCP server that connects AI agents to your Polar training, sleep, Nightly Recharge and continuous-sample data.
Unofficial project. Not affiliated with, endorsed by or supported by Polar Electro Oy. Polar is a trademark of its respective owner. Use this only with your own Polar account and in line with the Polar AccessLink API terms.
Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about training load, recovery and endurance - without copy-pasting numbers from Polar Flow.
Part of Delx Wellness, a registry of local-first wellness MCP connectors.
Polar has one of the deepest training-physiology stacks among consumer wearables - Nightly Recharge, continuous samples, PPI (pulse-to-pulse intervals), training targets, sport profiles, orthostatic and fitness tests. The Polar AccessLink Dynamic API v4 exposes this data, but with 16 fine-grained OAuth scopes and a structure that's harder to navigate than typical consumer APIs.
This package handles the OAuth dance locally, normalizes responses across the v4 endpoints, redacts GPS by default, and exposes Polar through the Model Context Protocol. Tokens never leave your machine.
You'll need a Polar AccessLink client (create one here) with redirect URI http://127.0.0.1:3000/callback.
npx -y polar-mcp-unofficial setup # interactive: paste client id + secret
npx -y polar-mcp-unofficial auth # opens browser, captures the OAuth code
npx -y polar-mcp-unofficial doctor # verifies you're readyRecommended scopes (request the ones matching the data you want):
activity:read calendar:read continuous_samples:read devices:read
nightly_recharge:read ppi_data:read profile:read routes:read
skin_contact:read sleep:read sports:read temperature_measurement:read
tests:read training_sessions:read training_targets:read user_subscription:read
Then add this to your MCP client config:
{
"mcpServers": {
"polar": {
"command": "npx",
"args": ["-y", "polar-mcp-unofficial"]
}
}
}For Claude Desktop, run setup --client claude and the snippet is written for you.
Three things to ask first:
Use polar_connection_status to check setup, then run polar_daily_summary.
Give me a 5-line training brief for today.
Call polar_weekly_summary with response_format=json. Identify my biggest
training-load/recovery bottleneck and give me a next-week plan.
Use the polar_training_load_investigation prompt, after=2026-04-01.
Walk me through my recent training sessions + Nightly Recharge.
This package uses the official Polar AccessLink Dynamic API v4. When this README says raw, it means the upstream Polar JSON for a supported endpoint - not raw device sensor streams.
| Data | Available | Notes |
|---|---|---|
| Daily activity + calendar | yes | Requires activity:read / calendar:read |
| Sleep + sleep/wake vectors | yes | Requires sleep:read |
| Nightly Recharge (recovery score) | yes | Requires nightly_recharge:read; supported devices |
| Training sessions + training targets | yes | Requires training_sessions:read / training_targets:read |
| Continuous samples (HR over time) | yes | Requires continuous_samples:read |
| PPI samples (pulse-to-pulse intervals, HRV-relevant) | yes | Requires ppi_data:read; supported devices |
| Temperature measurements | yes | Requires temperature_measurement:read; supported devices |
| Skin contact periods | yes | Requires skin_contact:read |
| Tests (fitness / orthostatic / running) | yes | Requires tests:read |
| Routes + GPS geometry | opt-in | GPS coordinates redacted unless raw mode |
| Sports + sport profiles + devices | yes | Catalog and user metadata |
| Live device telemetry | - | Not exposed by Polar AccessLink |
Start with these:
polar_connection_status- verify local setup, scopes and readiness before calling Polarpolar_daily_summary- sleep, activity, Nightly Recharge and training brief for todaypolar_weekly_summary- scorecard, comparison vs prior week, next-week plan
Auth & diagnostics
polar_capabilities,polar_agent_manifest,polar_privacy_audit,polar_cache_statuspolar_get_auth_url,polar_exchange_code,polar_revoke_access
Account
polar_get_account_data,polar_list_user_devices,polar_list_subscriptions
Activity & sleep
polar_list_activity,polar_list_calendarpolar_list_sleeps,polar_list_sleep_wake_vectorspolar_list_nightly_recharge
Heart & physiology (date range)
polar_list_continuous_samples,polar_list_ppi_samplespolar_list_temperature_measurements,polar_list_skin_contacts
Training
polar_list_training_sessions,polar_list_training_targets,polar_list_training_target_favoritespolar_list_tests
Sports & routes
polar_list_sports,polar_list_sport_profile_catalog,polar_list_sport_profilespolar_get_route- GPS coordinates redacted unless raw mode
polar_daily_checkin- practical daily training and recovery check-inpolar_weekly_review- review trends across activity, sleep and recoverypolar_training_load_investigation- investigate training sessions + recovery context
polar://capabilities,polar://agent-manifestpolar://summary/daily,polar://summary/weekly
- OAuth tokens are stored in
~/.polar-mcp/tokens.jsonwith0600permissions and are never returned by tools. - The server never prints access or refresh tokens.
POLAR_PRIVACY_MODEdefaults tostructured. Raw Polar JSON is opt-in viarawmode or per-call override.- GPS route geometry is redacted in
summaryandstructuredmodes - onlyrawmode exposes raw coordinates. - The MCP client never sees access or refresh tokens.
- This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or training prescription.
setup writes most of these into ~/.polar-mcp/config.json (0600). Manual env override is supported:
POLAR_CLIENT_ID=<client-id>
POLAR_CLIENT_SECRET=<client-secret>
POLAR_REDIRECT_URI=http://127.0.0.1:3000/callback
# Optional
POLAR_SCOPES="activity:read calendar:read continuous_samples:read ..."
POLAR_PRIVACY_MODE=structured # summary | structured | raw
POLAR_CACHE=sqlite # optional read-through cache
POLAR_TOKEN_PATH=~/.polar-mcp/tokens.json
POLAR_CACHE_PATH=~/.polar-mcp/cache.sqlitenpx -y polar-mcp-unofficial setup --client hermes --no-auth
npx -y polar-mcp-unofficial auth # run locally if browser auth is needed
npx -y polar-mcp-unofficial doctor --client hermes
hermes mcp test polarAfter Hermes config changes, use /reload-mcp or hermes mcp test polar. Don't restart the gateway for normal data access.
If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.polar-mcp/tokens.json to the server with chmod 600.
- Node.js 20+
- A Polar AccessLink client at https://admin.polaraccesslink.com with redirect URI
http://127.0.0.1:3000/callback
git clone https://github.com/davidmosiah/polarmcp.git
cd polarmcp
npm install
npm test
npm run buildTest with MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js- npm: https://www.npmjs.com/package/polar-mcp-unofficial
- Docs site: https://wellness.delx.ai/connectors/polar
- Legacy docs: https://polarmcp.vercel.app/
- GitHub: https://github.com/davidmosiah/polarmcp
- Delx Wellness registry: https://github.com/davidmosiah/delx-wellness
- Connector quality standard: https://github.com/davidmosiah/delx-wellness/blob/main/docs/connector-quality-standard.md
- Polar AccessLink Dynamic API v4 docs: https://www.polar.com/polar-api-v4/
MIT - see LICENSE.
This software is provided as-is. It is not a medical device, does not provide medical advice, and should not be used for diagnosis, treatment or training prescription. Always consult qualified professionals for medical or training concerns.