Échapper Journal / Guides
Connect Training Companion to Claude
A complete guide to adding Échapper as a remote connector, checking the training context and reviewing controlled changes.
Training Companion gives Claude access to the training context Échapper can retrieve from your connected Intervals.icu account. Claude can read that context and, through the full-access address, prepare controlled changes for you to review.
Before you start.
- Create or sign in to your Échapper account.
- Connect Intervals.icu from Échapper Account settings.
- Use Claude Free, Pro, Max, Team or Enterprise. Free accounts can currently add one custom connector.
- On Team or Enterprise, an Owner or Primary Owner must add the connector before members can connect it.
Your personal connector addresses appear only inside Échapper after you sign in and connect Intervals.icu. Never publish or share those addresses.
1. Copy the right address.
Open AI clients in Training Companion. Copy the address labelled Full access. It is intended for Claude and other clients that can use remote MCP write tools.
If you only want Claude to analyse data, you can use the read-only address instead. The read-only address never exposes create, update, delete, comment or profile-saving tools.
2. Add Échapper to Claude.
- Individual plan: open Customize → Connectors, choose +, then Add custom connector.
- Team or Enterprise owner: open Organization settings → Connectors → Add → Custom → Web.
- Name the connector Échapper.
- Paste the complete full-access address into the remote MCP server URL field.
- Choose Add, then complete the Échapper sign-in and authorization window.
Team and Enterprise members can then open Customize → Connectors, find Échapper under Custom and choose Connect.
3. Enable it in a conversation.
Start a new conversation, choose the + menu in the lower-left corner, open Connectors and enable Échapper for that conversation. A connector can be installed correctly without being enabled in the current conversation, so check this step when Claude does not use it.
4. Run a safe first check.
Read my rider context, current readiness and tomorrow’s calendar. Show the sources and assumptions you use.
A successful response should use your current context and keep recorded data, rider-provided information and interpretation distinct. It should not need to change anything.
5. Test a controlled change.
Ask Claude to prepare a small calendar change, such as adding an easy ride tomorrow. Training Companion should first return the exact proposed target, date and content. Nothing is sent to Intervals.icu at this stage.
Approve only if the preview is correct. The approval is short-lived and bound to the unchanged request. If Claude alters the request, Échapper requires a new preview and approval.
Research needs a stricter boundary.
Claude Research can invoke connector tools during a broader investigation. Use Échapper’s read-only address for Research, or disable write tools before starting it. Reserve the full-access connection for deliberate conversations where you are present to inspect each proposal.
If the connection does not work.
- No Add button: on Team or Enterprise, ask an Owner or Primary Owner to add the connector.
- Installed but unused: enable Échapper from the current conversation’s + → Connectors menu.
- Authorization failed: disconnect Échapper in Claude, then connect and authorize it again.
- Old tools: remove the custom connector and add it again with the current address.
- No training context: confirm that Intervals.icu is connected in Échapper Account.
Claude’s interface and plan rules can change. Check Anthropic’s current connector guide if a label or menu has moved.