Racewise, meet Claude.
Give Claude the training evidence behind your next question.
Your Claude account must offer custom connectors. On a team account, an owner may need to add the connector first.
Use a remote connector. This guide does not install a local desktop extension. Email sign-in and a live read-only Garmin request were validated on 22 September 2026. Write actions and automatic token renewal have not been validated with Claude.
Before you start
Have your invitation email, email verification access and assistant account ready. Create your invited account, confirm your timezone and check your Garmin connection. Keep the same Racewise email throughout. You can check the assistant connection before Garmin is connected.
Opening from WhatsApp on your phone?
For Claude 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.
https://racewise.run/guides/claude
Let your agent help
Copy these instructions into an assistant that can guide you or operate your browser. You handle verification codes and approve the connection. An assistant without browser controls can guide you while you do the clicks.
Read the full text
# Connect Racewise to Claude Type: Current guide. Scope: Claude setup; availability and validation limits are stated below. ## Table of contents - [Before starting](#before-starting) - [Connection details](#connection-details) - [Setup](#setup) - [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-09-20 Racewise status: Owner sign-in and live read validated — 22 September 2026 Eligibility: Your Claude account must offer custom connectors. On a team account, an owner may need to add the connector first. Use a remote connector. This guide does not install a local desktop extension. Email sign-in and a live read-only Garmin request were validated on 22 September 2026. Write actions and automatic token renewal have not been validated with Claude. ## 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 Claude 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/claude 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 - 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 your connectors: In Claude, open Customize → Connectors. 2. Add a custom connector: Select + → Add custom connector. Enter Racewise and the exact connection address from your invitation. For a team, ask an owner to add it in Organization settings → Connectors. 3. Choose authentication: Select Sign in now. Under OAuth client, select Register automatically. Leave request headers empty. Do not enter Auth0 credentials or a Resend key; Racewise registers the Claude client automatically. 4. Authorize Racewise: Add the connector, then choose Connect if prompted. Use your Racewise email sign-in and review the requested permissions. Use Register automatically; the published-identity and manual-client options were not tested. 5. Enable it in a conversation: Open a chat, use + → Connectors and enable Racewise. Try the read-only check below. ## 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 - [Claude: custom connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
Your connection address
It ends in /mcp. Your assistant may call this field “Server URL”. Copy the actual address from your invitation; the public website address is not a connection address.
Choose your permissions
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.
Connect step by step
Find your connectors
In Claude, open Customize → Connectors.
Add a custom connector
Select + → Add custom connector. Enter Racewise and the exact connection address from your invitation. For a team, ask an owner to add it in Organization settings → Connectors.
Choose authentication
Select Sign in now. Under OAuth client, select Register automatically. Leave request headers empty. Do not enter Auth0 credentials or a Resend key; Racewise registers the Claude client automatically.
Authorize Racewise
Add the connector, then choose Connect if prompted. Use your Racewise email sign-in and review the requested permissions. Use Register automatically; the published-identity and manual-client options were not tested.
Enable it in a conversation
Open a chat, use + → Connectors and enable Racewise. Try the read-only check below.
Check the connection
Try a read-only request first. An empty account is fine; the assistant should tell you what is missing.
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.
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.
Get one useful observation, three questions to try and help completing your training context.
Read the full 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 and training context saved in Racewise are separate. The memory preference does not guarantee Racewise is selected in every future chat; check that it is selected when asking about your data.
Review my training week
After Garmin is connected, select Racewise and use this prompt whenever you want a weekly review. It looks at your last seven days, your goals and one priority for the coming week.
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 something gets stuck
I cannot see the platform setting.
Check the eligibility above and your workspace policy. Menus can change. Use the official guide below; do not buy a different plan solely to try this pilot. Contact Arnaud if it is still missing.
The connection or callback is refused.
Check the exact address from your invitation, including /mcp. Contact Arnaud to check whether your assistant is enabled. Do not replace OAuth with an API key or copy a secret into chat.
I connected, but no Garmin data appears.
Open your Racewise account and check Garmin’s connection status. Ask your assistant which dates and measurements it could retrieve. Missing data is not evidence that no training occurred. If access is paused or the connection fails, contact Arnaud.
How do I disconnect?
Open your Racewise account and revoke the assistant connection. You can also remove it from the platform. Past conversations are managed separately by that platform.
Lost or expired invitation, or stuck on a step? Contact Arnaud. Include the step, short error message and device. Keep passwords, codes, invitation links and private training data out of your message.
Documentation checked 2026-09-20. Claude: custom connectors