Polar Mcp Unofficial

Name: Polar Mcp Unofficial
Author: davidmosiah

@davidmosiah

代码仓库

关于 Polar Mcp Unofficial

暂无概览

基本信息

分类

其他

传输方式

stdio

发布者

davidmosiah

提交者

David Batista

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "polar": {
      "command": "npx",
      "args": [
        "-y",
        "polar-mcp-unofficial"
      ]
    }
  }
}

工具

verify local setup, scopes and readiness before calling Polar

inventory supported data domains, scopes, privacy modes and recommended first calls without calling Polar APIs.

sleep, activity, Nightly Recharge and training brief for today

scorecard, comparison vs prior week, next-week plan

GPS coordinates redacted unless raw mode

概览

What is Polar Mcp Unofficial?

A local-first MCP server that connects AI agents to your Polar training, sleep, Nightly Recharge, and continuous-sample data. It handles the Polar AccessLink Dynamic API v4 OAuth dance locally, normalizes responses, redacts GPS by default, and never lets tokens leave your machine. Built for users of Claude, Cursor, Hermes, OpenClaw, and other MCP‑compatible agents who want to analyze training load, recovery, and endurance without copying numbers from Polar Flow.

How to use Polar Mcp Unofficial?

Install with three npm commands: npx -y polar-mcp-unofficial setup (paste your Polar AccessLink client id and secret), npx -y polar-mcp-unofficial auth (opens browser for OAuth), then npx -y polar-mcp-unofficial doctor to verify readiness. Add the server to your MCP client config with command npx -y polar-mcp-unofficial. For Claude Desktop, run setup --client claude to write the snippet automatically.

Key features of Polar Mcp Unofficial

Local‑first OAuth; tokens never leave your machine
Exposes Polar data via MCP tools, prompts, and resources
Privacy modes: summary, structured, raw (GPS redacted by default)
Supports 16 Polar AccessLink OAuth scopes
Built‑in diagnostics with doctor and connection_status
Caching via optional SQLite cache

Use cases of Polar Mcp Unofficial

Get a daily training and recovery brief with polar_daily_summary
Analyze weekly training‑load and recovery trends with polar_weekly_summary
Investigate recent training sessions alongside Nightly Recharge data
Inventory available data domains and scopes before making API calls

FAQ from Polar Mcp Unofficial

What data does Polar Mcp Unofficial expose?

It exposes all Polar AccessLink Dynamic API v4 endpoints you authorize: daily activity, sleep, Nightly Recharge, training sessions, continuous heart‑rate samples, PPI (pulse‑to‑pulse) intervals, temperature measurements, skin contact periods, fitness/orthostatic tests, routes (GPS redacted by default), sports, sport profiles, and devices. Live device telemetry is not available.

What are the runtime requirements?

Node.js 20+ and a Polar AccessLink client created at https://admin.polaraccesslink.com with redirect URI http://127.0.0.1:3000/callback.

Where are my OAuth tokens stored?

Tokens are stored in ~/.polar-mcp/tokens.json with 0600 permissions. The server never prints or returns access or refresh tokens, and the MCP client never sees them.

How does GPS privacy work?

In summary and structured privacy modes, GPS route geometry is redacted. Only raw mode exposes raw coordinates. The default mode is structured.

Is this an official Polar product?

No. This is an unofficial community project not affiliated with, endorsed by, or supported by Polar Electro Oy. Use it only with your own Polar account and in line with the Polar AccessLink API terms.