Racewise, meet Mammouth.

# Connect Racewise to Mammouth

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

## Table of contents

- [Before starting](#before-starting)
- [Connection details](#connection-details)
- [Setup](#setup)
- [1. Check the connection — no Garmin needed](#1-check-the-connection-no-garmin-needed)
- [2. My latest activity — after connecting Garmin](#2-my-latest-activity-after-connecting-garmin)
- [3. Understand my week](#3-understand-my-week)
- [4. Discuss my next run](#4-discuss-my-next-run)
- [I see “Paid access required” or no Custom MCP option](#i-see-paid-access-required-or-no-custom-mcp-option)
- [Authorization fails or the invitation expired](#authorization-fails-or-the-invitation-expired)
- [The assistant answers without using Racewise](#the-assistant-answers-without-using-racewise)
- [No activities appear, or access is paused](#no-activities-appear-or-access-is-paused)
- [What should I send back after the test?](#what-should-i-send-back-after-the-test)
- [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: Racewise pilot validation pending
Eligibility: Mammouth requires an active subscription for custom connectors. Your team must allow personal custom MCP connections.
Use your existing Mammouth subscription; do not buy another plan for this test. Racewise has not yet completed a live Mammouth connection test. Arnaud must enable and confirm the connection before you start. Your personal invitation supplies the correct account and server links.

## 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 Mammouth 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/mammouth
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. Have your invitation ready: Ask Arnaud for your personal Racewise invitation and the exact server URL for this test. Wait for him to confirm that Mammouth access is enabled. MCP simply means the connection that lets your assistant use Racewise. No installation or coding is required.
2. Open your Racewise account: Open your invitation, read the pilot information, accept it if you agree, and sign in with the invited email address. Enter any email verification code on the sign-in page yourself. Confirm your timezone. For the initial connection test, leave Garmin disconnected.
3. Open Mammouth settings: Sign in to your existing Mammouth account. Open https://mammouth.ai/app/account/settings and find Connectors. Keep the Racewise account page open in another tab.
4. Add Racewise: Choose Custom MCP. Read the trust notice; if you agree, select “I understand and trust this server”, then Continue. Enter Racewise as the name. Paste the exact server URL Arnaud supplied, including /mcp, with no spaces. Do not use the landing-page address racewise.run.
5. Choose the connection method: Select Automatic connection (OAuth, recommended), then Add Custom MCP. If the connection is waiting for authorization, select Connect. You do not need an API key, client secret or Garmin password in Mammouth.
6. Approve the requested permissions: The Racewise page opens. Sign in with the same invited email, read the permissions, and approve only if you agree. Start with read access; if write access is required unexpectedly, stop and ask Arnaud. Return to Mammouth after authorization.
7. Run the first check: Open a new Mammouth conversation and paste the first prompt below. If the chat offers a connector selector, select Racewise. A connected badge alone is not a successful test: the reply must come from an actual Racewise call. An empty account or Garmin not connected is expected at this stage.
8. Connect Garmin when your pilot access is ready: After Arnaud confirms the initial test and enables your athlete access, open your Racewise account and choose Connect Garmin. Enter Garmin credentials and any verification code only on that connection page. Never paste them into Mammouth chat. If access is paused, ask Arnaud rather than retrying. Then try the training prompts below.


### 1. Check the connection — no Garmin needed
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. Make an actual Racewise tool call now; do not answer from previous messages. If you cannot call it, explain what is blocking you.

### 2. My latest activity — after connecting Garmin
Use Racewise to retrieve my latest Garmin activity. Show its name, date, distance and duration, plus delivery, retrieved_at_utc and served_at_utc if available. Say whether the data came from Garmin or a cache. Do not invent missing values or change anything.

### 3. Understand my week
Use Racewise to summarize my last seven days of training. Show the dates covered, activities, total distance and duration where available. Separate recorded facts from your interpretation, mention missing data, and do not save or change anything.

### 4. Discuss my next run
Use Racewise to review my recent training and available recovery evidence before discussing my next run. Ask me about my current fatigue, pain, available time and next race if that context is missing. Explain your reasoning and uncertainty. Do not save advice, change a plan or send a workout to Garmin.

### I see “Paid access required” or no Custom MCP option
Check that you are signed in to the Mammouth account with your existing active subscription. A team administrator may need to allow personal connectors. Do not buy another plan just for this test; tell Arnaud what you see.

### Authorization fails or the invitation expired
Reopen the invitation Arnaud supplied and check you used its exact server URL. If it still fails, stop and send Arnaud the short error message. Do not send the full browser address: it may contain a private invitation or sign-in code.

### The assistant answers without using Racewise
Start a new chat, select Racewise if a connector selector is available, and repeat prompt 1. Ask it to state explicitly if no tool call was possible. A plausible answer is not proof of a working connection.

### No activities appear, or access is paused
No Garmin data is expected during the first connection check. Once athlete access is enabled, check the Garmin status on your Racewise account. If it says paused or fails to connect, contact Arnaud. Missing data does not mean you did no training.

### What should I send back after the test?
Tell Arnaud whether connection succeeded and whether prompt 1 made a real Racewise call. After Garmin is enabled, include the delivery and two timestamps from prompt 2. For an error, share a cropped screenshot or short message, hiding your email, private activity details and browser address. Never share passwords or verification codes. Contact: info@racewise.run.

## 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
- [Mammouth: connectors](https://info.mammouth.ai/docs/connectors/)

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. Make an actual Racewise tool call now; do not answer from previous messages. If you cannot call it, explain what is blocking you.

Use Racewise to retrieve my latest Garmin activity. Show its name, date, distance and duration, plus delivery, retrieved_at_utc and served_at_utc if available. Say whether the data came from Garmin or a cache. Do not invent missing values or change anything.

Use Racewise to summarize my last seven days of training. Show the dates covered, activities, total distance and duration where available. Separate recorded facts from your interpretation, mention missing data, and do not save or change anything.

Use Racewise to review my recent training and available recovery evidence before discussing my next run. Ask me about my current fatigue, pain, available time and next race if that context is missing. Explain your reasoning and uncertainty. Do not save advice, change a plan or send a workout to Garmin.

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.