Log inSubmit server
Polarmcp logo

Polarmcp

Local MCP access to Polar health, sleep, recovery, heart-rate, route and training data through AccessLink.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Polarmcp

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "polarmcp": {
      "command": "npx",
      "args": [
        "-y",
        "delx-wellness-hermes"
      ],
      "env": {
        "POLAR_MCP_HOST": "YOUR_VALUE_HERE",
        "POLAR_MCP_PORT": "YOUR_VALUE_HERE",
        "POLAR_MCP_TRANSPORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y delx-wellness-hermes

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

The polarmcp MCP server connects compatible AI agents to Polar AccessLink data through a local-first MCP process. It handles local OAuth setup, checks scopes and readiness, normalizes supported Polar responses, and keeps tokens on the user's machine. Agents can request daily or weekly wellness summaries, bounded heart-rate series, route data with GPS redaction, and synthetic demo payloads. Reach for it when an agent needs Polar training, sleep, recovery, or activity context without manually copying data from Polar Flow.

Use cases

  • Check Polar connection readiness before requesting wellness data
  • Generate daily sleep, activity, recovery, and training briefs
  • Compare weekly training load and recovery trends
  • Provide bounded heart-rate series for agent analysis
  • Inspect routes while keeping GPS coordinates redacted

Key features

  • Local Polar AccessLink OAuth flow
  • Daily and weekly wellness summaries
  • Sleep, Nightly Recharge, activity, and training data
  • Bounded agent-safe heart-rate series
  • Default GPS redaction for routes
  • Stdio and optional loopback Streamable HTTP transports

Tools9

What Polarmcp lets your agent do. Expand a tool for its parameters.

Self-reported~202 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · delx-wellness-hermes (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads207Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed9Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Polarmcp works

What polarmcp MCP server does

The polarmcp MCP server gives MCP-compatible agents access to data from a user's Polar account through the official Polar AccessLink Dynamic API v4. Supported information includes daily activity, sleep, Nightly Recharge, training sessions, training targets, continuous heart-rate samples, pulse-to-pulse intervals, temperature measurements, skin-contact periods, tests, sports metadata, devices, and routes.

Its tools cover both setup and data retrieval. polar_quickstart, polar_connection_status, and polar_data_inventory help an agent determine what is configured, which scopes are available, and which calls are appropriate. polar_demo provides synthetic payloads before real API requests. For analysis, polar_daily_summary produces a same-day brief, polar_weekly_summary compares recent and prior weeks, and polar_wellness_context returns recovery, sleep, and training load in a shared shape.

How it works

The server runs locally and performs the Polar OAuth flow on the user's machine. It uses the configured AccessLink client and requested scopes to call Polar's v4 endpoints, then normalizes responses for MCP tools. Access tokens remain local rather than being sent to a hosted service.

The default transport is stdio. An optional stateless Streamable HTTP mode listens on loopback, with a health endpoint at /health and MCP requests at /mcp. Routes use privacy protection by default: GPS coordinates are redacted unless raw mode is selected. The polar_heart_series tool returns a bounded, agent-oriented series from continuous samples rather than exposing an unrestricted stream.

Setup and configuration

Create a Polar AccessLink client and set its redirect URI to http://127.0.0.1:3000/callback. Run the interactive setup command with npx -y polar-mcp-unofficial setup, authenticate with npx -y polar-mcp-unofficial auth, and verify the result with npx -y polar-mcp-unofficial doctor. The client needs scopes matching the data the agent will request, such as sleep:read, nightly_recharge:read, continuous_samples:read, training_sessions:read, or routes:read.

Add the package as an MCP server with a command of npx and arguments -y polar-mcp-unofficial. The repository also documents a Claude Desktop setup command and a one-command Delx Wellness for Hermes setup. For HTTP mode, use --http; POLAR_MCP_HOST, POLAR_MCP_PORT, and POLAR_MCP_TRANSPORT=http configure the listener.

Tools and capabilities

Core capabilities include:

  • Check local authentication, scopes, privacy modes, cache state, and readiness.
  • List activity, calendar entries, sleep records, sleep-wake vectors, Nightly Recharge data, training sessions, targets, tests, sports, devices, and account information.
  • Retrieve continuous samples, PPI data, temperature measurements, and skin-contact periods when the account and device support them.
  • Produce daily and weekly summaries and a shared wellness context for downstream agent workflows.
  • List routes while redacting GPS coordinates by default.
  • Revoke access, inspect capabilities, and exchange an OAuth code locally.

Limitations and notes

The project is unofficial and is not affiliated with, endorsed by, or supported by Polar Electro Oy. Data availability depends on the user's device, account permissions, requested OAuth scopes, and the AccessLink API. Nightly Recharge, PPI, temperature, tests, and some other domains require both the relevant scope and supported Polar hardware or account data.

Polar AccessLink does not expose live device telemetry through this connector. A route's coordinates require an explicit raw-data choice. The package works with a user's own Polar account and should be used according to Polar AccessLink API terms.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Polarmcp

polarmcp is an MCP server that connects AI agents to a user's Polar AccessLink account through a local process. Its main tools check setup and scopes, provide daily and weekly wellness summaries, expose sleep, activity, recovery, training, and bounded heart-rate data, and redact route GPS coordinates by default.

Install it through npx by running `npx -y polar-mcp-unofficial setup`, then authenticate with `npx -y polar-mcp-unofficial auth` and run `npx -y polar-mcp-unofficial doctor`. Add `npx -y polar-mcp-unofficial` as the command in your MCP client configuration.

Yes, polarmcp can be wired into Cursor as an MCP server. The repository also documents standalone configuration for Claude Desktop and other MCP-compatible agents.

polarmcp redacts GPS coordinates from route results unless raw mode is requested. The server also runs locally and keeps Polar access tokens on the user's machine.

polarmcp supports activity, sleep, Nightly Recharge, training sessions and targets, continuous samples, PPI, temperature, skin contact, tests, sports, devices, account data, and routes. Availability depends on OAuth scopes and supported Polar devices.

Related MCP servers

All in Sports All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPolarmcp AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/polarmcp?style=directory)](https://allmcps.com/mcp/polarmcp)
HTML Embed
<a href="https://allmcps.com/mcp/polarmcp"><img src="https://allmcps.com/api/badge/polarmcp?style=directory" alt="Polarmcp on AllMCPs" /></a>