Remote connector

Racewise, meet Claude.

Give Claude the training evidence behind your next question.

Racewise pilot validation pending

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. Racewise’s Claude authorization flow still needs pilot validation.

Before starting, join with your invitation and confirm your timezone. Keep the same Racewise email throughout.

Racewise server URL

Use the exact MCP URL supplied with your invitation

Connect step by step

Find your connectors
In Claude, open Customize → Connectors.
Add a custom connector
Select + → Add custom connector. Enter Racewise and the server URL below. For a team, ask an owner to add it in Organization settings → Connectors.
Authorize Racewise
Add the connector, then choose Connect if prompted. Use your Racewise email sign-in and approve the access you want to grant. Leave advanced client credentials empty unless the Racewise operator supplied platform-specific setup instructions.
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.

Your first prompt

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.

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.

Agent setup instructions

# Connect Racewise to Claude

Documentation checked: 2026-09-20
Racewise status: Racewise pilot validation pending
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. Racewise’s Claude authorization flow still needs pilot validation.

## Connection details
- Server URL: Use the exact MCP URL supplied with your invitation
- Transport: Streamable HTTP
- Authentication: OAuth authorization code with PKCE, dynamic client registration
- First-use scope: garmin:read
- Account page: Use the account link supplied with your invitation
- Pilot enrollment: invitation required; do not create another identity.

## Setup
1. Find your connectors: In Claude, open Customize → Connectors.
2. Add a custom connector: Select + → Add custom connector. Enter Racewise and the server URL below. For a team, ask an owner to add it in Organization settings → Connectors.
3. Authorize Racewise: Add the connector, then choose Connect if prompted. Use your Racewise email sign-in and approve the access you want to grant. Leave advanced client credentials empty unless the Racewise operator supplied platform-specific setup instructions.
4. 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. Use the exact URL above. 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.

## 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)

Open the complete Markdown guide →

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.

The connection or callback is refused.

Check that the URL ends in /mcp. Ask the Racewise operator whether this platform has been enabled for the pilot. 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 the Garmin connection. Ask your assistant to report evidence coverage. Missing data is not evidence that no training occurred.

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.

Documentation checked 2026-09-20. Claude: custom connectors