1. PaceRunner
  2. Works with

PaceRunner's MCP server for runners

PaceRunner runs a remote MCP server at https://pacerunner.app/api/mcp. Any MCP client that supports remote servers with OAuth (Claude, ChatGPT and others) can connect to it, and then read your paces and calendar, import a training plan, send sessions to your Garmin with each one checked after it lands, and move sessions. It uses OAuth 2.1 with PKCE and dynamic client registration, needs a PaceRunner subscription, and never exposes your runs or health data.

What MCP is

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to outside tools. A service publishes a server that lists its tools, each with a name, a description and the inputs it takes; an assistant that speaks MCP can then call those tools on your behalf when a conversation needs them. A remote MCP server lives on the web, so you add it by URL and sign in, with nothing to install. For runners, that means the assistant you already plan with can act on the plan: in PaceRunner's case, by putting it on your Garmin.

Connection details

Server URLhttps://pacerunner.app/api/mcp
TransportStreamable HTTP, stateless
AuthorizationOAuth 2.1, authorization code with PKCE
Client registrationDynamic client registration (open), as Claude and ChatGPT expect
DiscoveryProtected-resource metadata (RFC 9728) pointing to PaceRunner's authorization server, which publishes its own metadata (RFC 8414)
Resource indicatorRequired: clients must send the server URL as the resource
TokensAccess tokens last one hour; refresh tokens keep the connection
Who can connectPaceRunner subscribers, after allowing the app on PaceRunner's consent page

How a client connects

  1. The client calls the server, gets a 401, and follows it to PaceRunner's authorization server.
  2. It registers itself, then sends you to PaceRunner to sign in (email code, Google or Apple).
  3. PaceRunner's consent page names the app and the site it returns to, and lists what it will be able to do. You choose Connect.
  4. The client swaps the code for tokens and starts calling tools.

Step-by-step setup for the two main assistants: Claude and ChatGPT.

The tools

ToolReadsWrites
get_profileYour paces by effort (easy, marathon, half marathon, threshold, 10K, 5K, mile), units, time zone, today's date, max heart rate, Garmin connection statusNothing
get_calendarPlans and sessions between two dates (default the next four weeks, at most 92 days), each with its status on GarminNothing
import_planA plan or chat as text, plus an optional start date (week 1) or end date (race day)A new plan in PaceRunner, with every session built at your paces; nothing goes to Garmin
send_and_checkA plan or a list of sessionsWorkouts on your Garmin Connect calendar, each read back and checked; sessions with open questions or no day are left out, with the reason
move_sessionA session and a new day, today or laterThe session's day, in PaceRunner and on Garmin, checked again; returns any safety-limit warning the move newly causes
remove_sessionsSessions to remove, today or later, and whether to keep them in the planThe sessions deleted from the plan and taken off Garmin, or only taken off Garmin
get_strengthStrength training in your plans: how often and with what, and the sessions between two dates with their exercises, sets, reps, weights and statusNothing
set_strengthA plan, once or twice a week (or none), and the equipment: no equipment, dumbbells or a gymStrength training in the plan, placed around your runs; sessions already on your watch are updated
update_strength_sessionA strength session (plan, week, slot) and a day, or send it to your watch or take it offThe session's day, or whether it's on your watch, checked like a run
set_strength_weightAn exercise and a weight in your own unitsThe weight for every session with that exercise, and on your watch with the sessions already there

The read tools are marked read-only, so clients that ask before acting can skip the prompt for them. Each call goes through the same code as PaceRunner's own pages: plan reading counts toward the same limits, sends go through the same queue, and every workout is read back from Garmin the same way.

What a session looks like

Ask your assistant for a plan, then ask it to use PaceRunner:

AskRead my PaceRunner paces, write me a 10-week 10K plan for a race on February 22 with three runs a week, import it, and send the first week to my Garmin.

The assistant calls get_profile, writes the plan with your real paces, calls import_plan, then send_and_check, and can follow up with get_calendar to report which sessions are on Garmin and checked.

Privacy

  • Never runs or health data. The tools expose paces and planned sessions only. Completed runs, heart-rate data, sleep and everything else Garmin holds stay out of reach of any connected app.
  • Checked on every request. The token's signature, issuer and audience are verified, your consent for that app is checked (so Disconnect under Connected apps on Profile ends access at once), and your subscription is checked on every tool call.
  • Your Garmin password is never involved: PaceRunner connects to Garmin through Garmin's own sign-in, separately.

Limits

  • Garmin only: sends go to Garmin Connect.
  • Subscribers only.
  • Sessions are sent for today or later; long plans go to Garmin over a few hours, nearest first.
  • If you sign in with an emailed link, open it in the same browser that started the connection.
  • Not yet in Claude's or ChatGPT's directories; add it as a custom connector or app.
  • Pace re-targeting after a time trial isn't shown through the tools yet; use PaceRunner itself for that.

Questions

What is PaceRunner's MCP server URL?
https://pacerunner.app/api/mcp. Add it as a custom connector in Claude, or as a custom app in ChatGPT's developer mode.
Which MCP clients work?
Any client that supports remote MCP servers with OAuth, including Claude and ChatGPT.
Is it a Garmin MCP server?
It sends workouts to Garmin Connect through Garmin's official Training API, but it doesn't expose your Garmin data. See Garmin MCP servers for the difference.
Does it need a subscription?
Yes. Connecting and every tool call need an active PaceRunner subscription (7-day free trial, then $9.99 a month or $79.99 a year).

Checked November 20, 2026