Write to your diary
Create, edit, and delete structured training targets (warmup / repeat / cooldown) — the AccessLink API can only read.
polar-flow-mcp
Schedule structured workouts in your Polar Flow diary from a conversation with your AI assistant — no app, no UI navigation.
“Schedule a 5×1km threshold session for Thursday.” Your assistant calls
create_training_target and the workout appears in your Polar Flow diary.
polar-flow-mcp is a single-user MCP server
that drives the reverse-engineered Polar Flow web API (flow.polar.com) —
the same API the browser app uses — so any MCP client can perform write
operations the official read-only AccessLink API cannot.
Find your way around
Section titled “Find your way around”These docs follow the Diátaxis framework — four kinds of documentation for four kinds of need.
TutorialsLearning-oriented. Go from a fresh checkout to talking to your MCP client in about five minutes.
How-to GuidesTask-oriented. Deploy, expose securely, create workouts, install the skill.
ReferenceInformation-oriented. Every MCP tool, environment variable, and HTTP endpoint.
ExplanationUnderstanding-oriented. Why the web API, the design decisions, and the security model.
What it does
Section titled “What it does”Read your training
List completed sessions, per-week totals, and aggregated progress summaries over any date range.
Single binary
A FROM scratch image (~14 MB), no database, no CGO — just a
chmod-600 cookie jar for session persistence.
Public or private
Run it locally over stdio or HTTP, or expose it publicly as a remote connector (e.g. Claude.ai) behind its own OAuth 2.1 server.