A
licenseB
qualityA
maintenanceLocal-first MCP server that connects AI agents to your Garmin sleep, HRV, Body Battery, stress, training readiness and activities, keeping tokens on your machine.
2
42
227 npm
12
MIT
Polar MCP
by davidmosiah
Related Servers
Alternatives to Polar MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceLocal-first MCP server that connects AI agents to your Fitbit activity, sleep, heart-rate, HRV, SpO2 and weight data.33135 npm4MIT
- FlicenseAqualityFmaintenanceAn MCP server for the Polar AccessLink API. Connect your Polar fitness data to Claude AI - access workouts, sleep analysis, recovery metrics, heart rate data, and more.256-
- AlicenseBqualityAmaintenanceLocal-first MCP server that connects AI agents to your Withings body, sleep, activity and heart data.23451 npm5MIT
- AlicenseBqualityAmaintenanceLocal-first MCP server that connects AI agents to your Oura Ring readiness, sleep, activity, and HRV data. Tokens never leave your machine.27477 npm4MIT
- AlicenseBqualityAmaintenancePrivacy-first, unofficial WHOOP MCP server for AI health, sleep, recovery, and performance agents.30671 npm14MIT
TDQS
B3.3/5.0
Scored across 38 tools
Disambiguation3/5
The many polar_list_* tools are well-differentiated by data domain, but several meta/informational tools overlap heavily (polar_capabilities, polar_data_inventory, polar_agent_manifest, polar_demo, polar_quickstart) and the diagnostic tools (polar_connection_status, polar_cache_status, polar_privacy_audit) have blurred boundaries. Also polar_list_continuous_samples vs polar_heart_series requires a judgment call.
Naming Consistency4/5
Almost all tools use a consistent polar_ prefix with snake_case and verb_noun patterns (list_, get_, exchange_, revoke_). Minor deviations exist: polar_profile_get puts the verb after the noun while polar_get_account_data does the opposite.
Tool Count2/5
38 tools is well above the typical 15-tool ceiling and feels heavy for a read-focused Polar data connector. While many list endpoints are domain-specific, the large cluster of meta, auth, and diagnostic tools adds considerable surface area.
Completeness4/5
The server covers a broad range of Polar data domains (activity, sleep, nightly recharge, training, routes, devices, sports, tests, etc.) with read access matching Polar AccessLink's read-only nature. Auth flow and profile lifecycle are present; minor gaps include no generic get-by-id for most record types.
Maintenance
ActivityActive
ResponsivenessSlow