Polarmcp

Name: Polarmcp
Author: davidmosiah

by davidmosiahversion 0.3.6i★ –iRuns on your computer

Registry nameio.github.davidmosiah/polarmcp

Install

Overview

Description from the maker (original English)

Privacy-first unofficial Polar AccessLink v4 MCP server for AI health, sleep and training agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health
You need to fill in: POLAR_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: POLAR_CLIENT_ID, POLAR_CLIENT_SECRET, POLAR_REDIRECT_URI, POLAR_TOKEN_PATH, POLAR_PRIVACY_MODE, POLAR_CACHE, POLAR_CACHE_PATH, POLAR_NO_CACHE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "polarmcp": {
      "command": "npx",
      "args": [
        "-y",
        "polar-mcp-unofficial"
      ],
      "env": {
        "POLAR_CLIENT_ID": "your-value",
        "POLAR_CLIENT_SECRET": "your-value",
        "POLAR_REDIRECT_URI": "your-value",
        "POLAR_TOKEN_PATH": "your-value",
        "POLAR_PRIVACY_MODE": "your-value",
        "POLAR_CACHE": "your-value",
        "POLAR_CACHE_PATH": "your-value",
        "POLAR_NO_CACHE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add polarmcp --env POLAR_CLIENT_ID=your-value --env POLAR_CLIENT_SECRET=your-value --env POLAR_REDIRECT_URI=your-value --env POLAR_TOKEN_PATH=your-value --env POLAR_PRIVACY_MODE=your-value --env POLAR_CACHE=your-value --env POLAR_CACHE_PATH=your-value --env POLAR_NO_CACHE=your-value -- npx -y polar-mcp-unofficial

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "polarmcp": {
      "command": "npx",
      "args": [
        "-y",
        "polar-mcp-unofficial"
      ],
      "env": {
        "POLAR_CLIENT_ID": "your-value",
        "POLAR_CLIENT_SECRET": "your-value",
        "POLAR_REDIRECT_URI": "your-value",
        "POLAR_TOKEN_PATH": "your-value",
        "POLAR_PRIVACY_MODE": "your-value",
        "POLAR_CACHE": "your-value",
        "POLAR_CACHE_PATH": "your-value",
        "POLAR_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "polarmcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "polar-mcp-unofficial"
      ],
      "env": {
        "POLAR_CLIENT_ID": "your-value",
        "POLAR_CLIENT_SECRET": "your-value",
        "POLAR_REDIRECT_URI": "your-value",
        "POLAR_TOKEN_PATH": "your-value",
        "POLAR_PRIVACY_MODE": "your-value",
        "POLAR_CACHE": "your-value",
        "POLAR_CACHE_PATH": "your-value",
        "POLAR_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

POLAR_CLIENT_ID env
Polar OAuth client ID. Optional when configured with polar-mcp-server setup.
POLAR_CLIENT_SECRET secret env
Polar OAuth client secret. Prefer polar-mcp-server setup so this secret is stored in ~/.polar-mcp/config.json instead of MCP client config.
POLAR_REDIRECT_URI env
Redirect URI configured in the Polar AccessLink admin. Optional when configured with polar-mcp-server setup.
POLAR_TOKEN_PATH env
Optional local path for OAuth tokens. Defaults to ~/.polar-mcp/tokens.json.
POLAR_PRIVACY_MODE env
Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Polar AccessLink payloads for supported endpoints.
POLAR_CACHE env
Optional SQLite cache toggle. Set to true or sqlite to enable.
POLAR_CACHE_PATH env
Optional local SQLite cache path. Defaults to ~/.polar-mcp/cache.sqlite.
POLAR_NO_CACHE env
Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account davidmosiah, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 870 servers in this category
Published to the registry more recently than 23% of the other 870 servers in this category
Basic checks equal to or better than 100% of the other 870 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Polarmcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: POLAR_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.6) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Langcare MCP FHIR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 6 days ago

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago

Install

Langcare MCP FHIR

by langcare

An MCP FHIR server written in Go for EMR systems like Epic and Cerner

Runs on your computer★ 70MITUpdated 9 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Upgrading to 0.6.0: read the migration guide for local-only HTTP, disabled authenticated-response caching, and stricter input/profile limits.

Polar MCP

Give your AI agent your Polar Nightly Recharge, training load, PPI and HRV data — locally.

Local-first MCP server — tokens never leave your machine .

⚡ One-command install with Delx Wellness for Hermes:

npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y polar-mcp-unofficial --http

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

Env: POLAR_MCP_HOST, POLAR_MCP_PORT, POLAR_MCP_TRANSPORT=http.

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.

If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.

Why this exists

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.

Setup in 60 seconds

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 ready

Recommended 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.

Try it with your agent

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.

Data availability

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

Tools

Start with these:

polar_quickstart - personalized 3-step setup walkthrough that adapts to what's already configured
polar_connection_status - verify local setup, scopes and readiness before calling Polar
polar_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Polar APIs.
polar_demo - synthetic example payloads so agents see the contract before calling the real API
polar_daily_summary - sleep, activity, Nightly Recharge and training brief for today
polar_weekly_summary - scorecard, comparison vs prior week, next-week plan
polar_wellness_context - Nightly Recharge, sleep and training load in the shared wellness_context shape

Auth & diagnostics

polar_capabilities, polar_agent_manifest, polar_privacy_audit, polar_cache_status
polar_get_auth_url, polar_exchange_code, polar_revoke_access

Account

polar_get_account_data, polar_list_user_devices, polar_list_subscriptions

Shared wellness profile (local, never Polar data)

polar_onboarding, polar_profile_get, polar_profile_update — the Delx Wellness profile shared with the other connectors; stores only what the user typed, never tokens or biomarkers

Activity & sleep

polar_list_activity, polar_list_calendar
polar_list_sleeps, polar_list_sleep_wake_vectors — sleep lists hydrate available dates with the v4 sleep-result, sleep-evaluation, and sleep-score features by default
polar_list_nightly_recharge

Heart & physiology (date range)

polar_heart_series — agent-safe-series/v1 bounded HR from continuous samples (prefer this for agents)
polar_list_continuous_samples, polar_list_ppi_samples
polar_list_temperature_measurements, polar_list_skin_contacts

Training

polar_list_training_sessions, polar_list_training_targets, polar_list_training_target_favorites
polar_list_tests

Sports & routes

polar_list_sports, polar_list_sport_profile_catalog, polar_list_sport_profiles
polar_get_route - GPS coordinates redacted unless raw mode

Prompts

polar_daily_checkin - practical daily training and recovery check-in
polar_weekly_review - review trends across activity, sleep and recovery
polar_training_load_investigation - investigate training sessions + recovery context

Resources

polar://capabilities, polar://agent-manifest, polar://inventory
polar://summary/daily, polar://summary/weekly
polar://account-data, polar://latest/sleep

Privacy & security

OAuth tokens are stored in ~/.polar-mcp/tokens.json with 0600 permissions and are never returned by tools.
The server never prints access or refresh tokens.
POLAR_PRIVACY_MODE defaults to structured. Structured mode preserves the complete upstream physiological payload while removing secret/GPS fields; normalized aliases are additive and never replace nested v4 objects. Raw Polar JSON is opt-in via raw mode or per-call override.
GPS route geometry is redacted in summary and structured modes - only raw mode exposes raw coordinates.
Date formats and supported features are validated per endpoint. Feature queries that Polar limits to one day are hydrated one available date at a time.
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.

Configuration

setup writes most of these into ~/.polar-mcp/config.json (0600). Manual env override is supported:

POLAR_CLIENT_ID=<client-id>

POLAR_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 # no effect: authenticated responses are never cached POLAR_TOKEN_PATH=~/.polar-mcp/tokens.json POLAR_CACHE_PATH=~/.polar-mcp/cache.sqlite

Hermes / remote setup

npx -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 polar

After 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.

Requirements

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

Development

git clone https://github.com/davidmosi

Only the beginning is shown; read the rest in the repo

Polarmcp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Langcare MCP FHIR

README from the maker

HTTP (v2 stateless)

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

Why this exists

Setup in 60 seconds

Try it with your agent

Data availability

Tools

Prompts

Resources

Privacy & security

Configuration

Optional

Hermes / remote setup

Requirements

Development