Racewise, meet ChatGPT.

# Connect Racewise to ChatGPT

Type: Current guide. Scope: ChatGPT setup; availability and validation limits are stated below.

## Table of contents

- [Before starting](#before-starting)
- [Connection details](#connection-details)
- [Setup](#setup)
- [Optional: add the Racewise icon](#optional-add-the-racewise-icon)
- [Instructions for an assisting agent](#instructions-for-an-assisting-agent)
- [Verify](#verify)
- [Once connected, get to know Racewise](#once-connected-get-to-know-racewise)
- [Review my training week](#review-my-training-week)
- [Disconnect](#disconnect)
- [Official sources](#official-sources)
Documentation checked: 2026-10-07
Racewise status: Read access tested in the pilot
Eligibility: Use ChatGPT on the web with access to custom MCP servers in Plugins. Your account and workspace policies must allow this setting.
A previous pilot connection passed read, reconnect and revocation checks. These instructions were checked against official documentation on 7 October 2026; fresh registration with the latest backend still needs validation. You may need help from Arnaud to finish setup.

## Before starting
Have your invitation email and email verification access ready. Use the same
invited identity throughout. Check your assistant's eligibility first.
Follow account -> Garmin status -> assistant connection -> first training question.
An initial assistant connection check can run before Garmin is connected.
For ChatGPT setup, use the web interface. Phone and in-app-browser setup have not been validated in this pilot. You can continue in a browser on your computer: copy this guide link and open it there, with your invitation email ready. Setup on the web does not establish that every feature works in the mobile app.
If continuing on a computer, open this guide there: https://racewise.run/guides/chatgpt
For lost or expired invitations, contact Arnaud at info@racewise.run.

## Connection details
- Connection address: Find the exact connection address in the personal invitation. It ends in /mcp. This public website does not supply it; do not infer an endpoint from this domain.
- Transport: Streamable HTTP
- Authentication: OAuth authorization code with PKCE, dynamic client registration
- First-use scope: garmin:read
- Account page: Use the account link in the invitation, or sign in at https://racewise.run/account/login
- Optional icon download: [ChatGPT connection icon](https://racewise.run/racewise-icon.png)
- Pilot enrollment: invitation required; do not create another identity.

Read access is included when you connect; it has no checkbox. For a read-only connection, leave every optional permission checkbox unchecked, then select Connect with selected permissions. The checkboxes add write access.

## Setup
1. Find the connection setting: Open ChatGPT Plugins and select + → Add custom MCP server (some screens say Create custom MCP server). If this setting is absent, check your account and workspace policy or contact Arnaud before continuing.
2. Add Racewise: Name it Racewise. Under Connection, use the public server URL option and paste the exact connection address from your invitation, including /mcp. ChatGPT labels this field Server URL. The public website address is not your connection address.
3. Choose authentication: Choose OAuth. If offered a registration choice, select dynamic client registration (DCR). Leave static client credentials empty and do not select CIMD. Never enter an Auth0 or Garmin secret into ChatGPT.
4. Create and authorise the plugin: Read the trust warning and acknowledge it only if you agree, then select Create as a plugin. When Racewise asks you to sign in, use your invited email and review the permissions yourself. Start with read access; if extra access is unexpectedly required, stop and contact Arnaud.
5. Install and use Racewise: Find Racewise in your personal plugins and install it. Start a new conversation, type @ and select Racewise, then run the connection check in this guide. If your ChatGPT interface offers Chat and Work, use Work as described in the official quickstart. Menu labels can vary.

## Optional: add the Racewise icon
In the connection form, choose Choose icon and upload the PNG linked here. The observed form accepts PNG up to 10 KB; this 256 × 256 icon fits. You can skip the icon and continue.
https://racewise.run/racewise-icon.png




## Instructions for an assisting agent
Help me configure this connection only if my platform and Racewise pilot access
are eligible. Obtain the exact connection address before acting. Inspect the existing connection before
creating a duplicate. Explain any requested permissions and let me complete
email verification, Garmin login and the final OAuth consent myself.
Do not request, copy, print or store passwords, email codes, refresh tokens,
Auth0 credentials or service secrets in chat or configuration files.
Do not disable authentication, expand server callback allowlists, purchase a
subscription, change my region or enable write access to work around a failure.
If a callback is refused or a setting is missing, report the blocker.

## Verify
Ask: Use Racewise to show my saved training context and timezone. Do not change anything. Tell me if Garmin is not connected or if evidence is missing.
Report success only after an actual Racewise tool call succeeds. Check that the
timezone/context belongs to me. Stop if it belongs to someone else. Do not infer
success from a connector appearing in a list. An empty account is not an error.
No training data needs to be read or changed for this initial check.

## Once connected, get to know Racewise
Once Racewise is connected, select it in your chat and paste this prompt. It asks for one useful observation and three questions to try, then helps fill gaps in your goals and training context. You approve anything saved in Racewise. If assistant memory is unavailable, it gives you a preference to add to your custom instructions.

```text
I've connected Racewise. Make a read-only Racewise call to check that it works, then look at my latest available training data and saved goals and constraints. Give me one useful observation in plain language and three questions I could ask next. Briefly say what is available, what needs extra permission and what is unavailable. If the connection fails or Garmin is not connected, clearly explain the next step. Never imply you checked data when you did not, or invent an observation when data is missing.

Ask me up to three questions about important gaps in my goals, available training time or other constraints. Offer to save my answers in Racewise, and wait for my approval before doing so.

Please save this preference in your assistant memory, if that feature is available: "Whenever we discuss my own training, fitness progress, recovery, workouts or race preparation, use relevant Racewise data and saved context before giving personalised advice, unless I ask you not to. Check my latest Racewise data before answering. Tell me if anything is missing or out of date." Tell me whether you actually saved it. If you cannot save it across chats, give me the exact text to add to my custom instructions instead.

This preference authorises relevant reads only. Ask for my explicit approval before saving or changing anything in Racewise, or sending workouts or events to Garmin.
```

Assistant memory is separate from context saved in Racewise. Neither guarantees
that Racewise is selected in every future conversation.

## Review my training week
After Garmin is connected, select Racewise and use this prompt whenever you want a weekly review:

```text
Use Racewise to review my last seven days of training alongside my saved goals and constraints. Tell me what went well, what is worth discussing and one priority for the coming week. Show the dates covered. Tell me if anything is missing or out of date, and ask about my goals if they are not saved. Clearly separate what my data shows from your suggestions. Do not save or change anything, or send workouts or events to Garmin.
```
If Garmin is unavailable or no data is returned, check its status in your Racewise
account and contact Arnaud at info@racewise.run. Do not treat missing data as no training.

## Disconnect
Revoke this assistant from the Racewise account page. Removing it from the
assistant does not erase information already present in conversations.

## Official sources
- [OpenAI: custom MCP servers](https://developers.openai.com/api/docs/guides/custom-mcp-server)
- [OpenAI: connect and test](https://developers.openai.com/plugins/deploy/connect-chatgpt)
- [OpenAI: plugin quickstart](https://developers.openai.com/plugins/quickstart)

I've connected Racewise. Make a read-only Racewise call to check that it works, then look at my latest available training data and saved goals and constraints. Give me one useful observation in plain language and three questions I could ask next. Briefly say what is available, what needs extra permission and what is unavailable. If the connection fails or Garmin is not connected, clearly explain the next step. Never imply you checked data when you did not, or invent an observation when data is missing.

Ask me up to three questions about important gaps in my goals, available training time or other constraints. Offer to save my answers in Racewise, and wait for my approval before doing so.

Please save this preference in your assistant memory, if that feature is available: "Whenever we discuss my own training, fitness progress, recovery, workouts or race preparation, use relevant Racewise data and saved context before giving personalised advice, unless I ask you not to. Check my latest Racewise data before answering. Tell me if anything is missing or out of date." Tell me whether you actually saved it. If you cannot save it across chats, give me the exact text to add to my custom instructions instead.

This preference authorises relevant reads only. Ask for my explicit approval before saving or changing anything in Racewise, or sending workouts or events to Garmin.