Scoped OAuth 2.1
You approve exactly what Claude can see and do before the connector is active. Nothing is shared by default.
Claude speaks MCP natively. Vertical's connector gives it your real training: every run, your load, your zones, your plan. Ask like you'd ask a coach, and get answers from your actual data.
Two ways to get there
The GitHub route
Clone a community Garmin MCP server, set up a Python environment, generate API tokens, and drop your Garmin password into a config file. Restart Claude Desktop and you get raw JSON back: no interpretation, no context, no plan.
python -m venv venv
pip install garminconnect mcp
export GARMIN_PASSWORD=... # yours, in plaintextVertical for Claude
Connect through OAuth: no config file, no terminal, no password ever touching Claude. Vertical turns your training data into a coach that reads your zones, your load and your plan, and talks back in plain language instead of a JSON blob.
Try asking
“What's my workout today and why?”
“Did I sleep-walk into overtraining this month?”
“Compare my last three long runs.”
“I have a 10K in six weeks. What should this week look like?”
Not a data dump
Claude gets typed, interpreted values instead of a CSV export: fitness, fatigue and form (CTL, ATL, TSB), pace zones from your critical-power fit, your current readiness, and where you sit in your plan. It's grounded in your data and a curated library of 500+ peer-reviewed papers, so answers stay tied to your training instead of a generic guess.
Read and write
Read-only elsewhere
Vertical for Claude
Early access
Create your Vertical account and connect your watch, Garmin, COROS or Polar, at getvertical.ai.
One click from your account page once it's live. Early access starts at signup, and we'll email you the moment your connector is ready.
Open Claude and ask about today's workout, this week's plan, or your last long run.
No terminal. No API keys. No config files. OAuth only, the same sign-in flow you'd use for any app.
Privacy
You approve exactly what Claude can see and do before the connector is active. Nothing is shared by default.
Turn the connector off from Claude's connector settings or from Vertical, whichever you reach first. Access ends immediately.
Vertical authenticates with Garmin, COROS and Polar through their official device APIs. Your watch password never touches Claude or Vertical's connector layer.
Your training data is used to coach you. It is not used to train Anthropic's or Vertical's models.
Not an official one from Garmin. Garmin has no public API for personal accounts, so the Garmin MCP servers you find on GitHub are unofficial: they need your Garmin username and password dropped into a config file, and they hand back raw JSON with no coaching layer. Vertical connects to Garmin, COROS and Polar through their official device APIs, with OAuth, and gives Claude interpreted training data instead of a data dump.
Custom connectors like Vertical's follow whatever plan requirements Anthropic sets for connectors on your Claude plan, and that has changed before, so we won't promise specifics here. What we can promise: no Vertical feature on this page requires anything beyond your Vertical trial and however Claude gates connectors for your account.
Only what you approve during OAuth. That typically means your recent activities, your current training load and zones, and your active plan, all through Vertical, the same account you already control from the Vertical app. Claude never sees your watch login, and you can narrow or revoke access at any time.
Yes, with your explicit confirmation. Claude can propose a scheduling change or a structured workout, but nothing gets written to your calendar or your watch until you say go. Once you confirm, Vertical pushes the structured workout to Garmin, COROS or Polar, the same way it does from the Vertical app.
Strava ships its own official MCP connector for subscribers, and it's read-only: it can describe your activities back to an AI, but it can't write anything, and third-party apps still can't use Strava data to power AI features under Strava's API terms. Vertical doesn't route through Strava at all. It syncs Garmin, COROS and Polar directly, and it can write back: scheduling and structured workouts, not just descriptions.
Remote MCP connectors are built to work across Claude's surfaces, desktop and mobile alike, since the connector runs on Vertical's servers rather than on your machine. We're being deliberately careful not to overclaim specifics before the connector is publicly live; exact availability will be confirmed when early access opens.
If you want a coach that plans your season, adapts your week automatically and talks to you by voice, yes, that's the full Vertical app. The Claude connector is a different way in: it brings that same coach and the same training data into a conversation you're already having in Claude, for the moments you'd rather ask than open another app.
Vertical also has a page for ChatGPT at /chatgpt/, and a general MCP connector for any MCP-compatible client at /mcp/. If you use something else and want Vertical wired into it, email [email protected] and tell us what you're running.
Meet your coach
Card required. Cancel any time before the trial ends.
7-day free trial · card required · cancel anytime