Racewise, meet Vibe (Mistral).

# Connect Racewise to Vibe (Mistral)

Type: Current guide. Scope: Vibe (Mistral) setup; availability and validation limits are stated below.

## Table of contents

- [Before starting](#before-starting)
- [Connection details](#connection-details)
- [Setup](#setup)
- [I cannot add a custom connector](#i-cannot-add-a-custom-connector)
- [Racewise shows Invitation-only pilot after sign-in](#racewise-shows-invitation-only-pilot-after-sign-in)
- [The connection needs more information or authorization fails](#the-connection-needs-more-information-or-authorization-fails)
- [Vibe answers without calling Racewise](#vibe-answers-without-calling-racewise)
- [Tools are missing after an update](#tools-are-missing-after-an-update)
- [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-27
Racewise status: Free-account connection and live read validated — 27 October 2026
Eligibility: Use Vibe Work on the web with permission to add custom MCP connectors. Mistral requires an administrator; on Free, Pro and Student plans, the account owner is the administrator. Organization policy may restrict access.
Racewise OAuth sign-in, tool discovery and an actual read-only connected_providers call succeeded in a free Vibe Work account on 27 October 2026. This verifies the assistant connection, not Garmin activity or health retrieval. Optional write permissions were granted by the tester but not exercised. Write actions, token renewal and mobile compatibility remain unvalidated. Contact Arnaud if setup fails; do not change OAuth settings to work around it.

## 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 Vibe (Mistral) 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/vibe
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: Open your Racewise invitation, sign in with the invited email and confirm your timezone. Ask Arnaud to confirm that Vibe access is enabled before testing. You can check the assistant connection before connecting Garmin.
2. Open Vibe Work: Use the Work experience in your browser. Open Context → Connectors from the sidebar (Contexte → Connecteurs in French). These steps cover the web assistant; Vibe Code and its command-line MCP configuration are separate.
3. Add a custom connector: Choose Add connector (Ajouter un connecteur), then Add custom connector (Ajouter un connecteur personnalisé) on the Marketplace page. Some versions show a Custom MCP Connector tab instead. If unavailable, ask your organization administrator. Do not buy a different plan just to try this pilot.
4. Enter the connection details: Use racewise as the connector name, with no spaces. Paste the exact Server URL from your invitation, including /mcp. The public website address is not your connection address. The description is optional.
5. Connect with OAuth: Wait for automatic authentication detection, then select Add connector or Connect when enabled. Vibe documents OAuth with dynamic client registration. Complete the Racewise sign-in and review consent yourself. Read access is included and has no checkbox. For a read-only connection, leave every optional checkbox unchecked, then select Connect with selected permissions. The checkboxes add write access. If asked for an API key, password in a connector field or manual client secret, stop and contact Arnaud.
6. Review function permissions: Under Connectors → My Connectors, open Racewise and review its Tools section (Outils in French; some versions use a Functions tab). The tested interface groups Interactive tools under Ask (Interactif → Demander) and read-only tools under Allow (Lecture seule → Autoriser). Keep write tools on Ask; saving context and publishing workouts or events require separate permission and explicit approval.
7. Enable Racewise in a conversation: Start a Work conversation. Open the + settings menu → Connectors (Connecteurs), then select racewise. Some versions use + or / → Tools instead. Confirm Racewise appears in the composer, then run the read-only connection check below and approve the read call if asked. A Connected indicator alone does not prove the call worked.


### I cannot add a custom connector
Check that you are using Work and have administrator permission. Ask your organization administrator if the setting is absent. Availability in Mistral documentation does not establish that Racewise access is enabled for your account.

### Racewise shows Invitation-only pilot after sign-in
Use the invited Racewise email for the server in your invitation. Production and staging accounts are separate; a staging identity does not grant production access. In Vibe, open the existing Racewise connector and choose Connect (Se connecter) to start sign-in again with the correct email. Do not create another connector or account to retry.

### The connection needs more information or authorization fails
Check the exact invitation address, including /mcp. If OAuth fails or a callback is refused, stop and contact Arnaud with a short error message. Hide invitation links, browser addresses, verification codes and tokens. Do not switch to static credentials or guess a callback address.

### Vibe answers without calling Racewise
Enable Racewise under the conversation’s Tools menu and repeat the read-only check, asking for an actual tool call. If no call is possible, ask Vibe to state the blocker. Do not accept remembered training details as a connection test.

### Tools are missing after an update
Mistral documents that custom MCP connectors do not yet support dynamic tool discovery, resources or automatic prompt templates. Ask Arnaud to check the connector’s discovered tools before relying on a new feature. Do not repeatedly reconnect or retry a write whose outcome is unknown.

## 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
- [Mistral: custom MCP connectors](https://docs.mistral.ai/vibe/work/connectors/mcp-connectors)
- [Mistral: use connectors in Work](https://docs.mistral.ai/vibe/work/connectors)
- [Mistral: choose Work or Code](https://docs.mistral.ai/vibe/choose-chat-work-code)

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.