Connect your AI assistant
RideIndex hands your training data to the assistant you already use — it reads your fitness, rides, routes and calendar, and can build and schedule workouts if you let it.
https://rideindex.app/api/mcp- 1In your assistant, add a custom connector and paste the URL above.Not seeing the option? Custom connector support varies between assistants and plans.
- 2It sends you to RideIndex to sign in and approve access. Choose read-only, or allow writes so it can build and schedule workouts too. No token to copy — the connector registers itself.
- 3Start a chat and ask it something. It reads your data and answers.
- “Build my 2x20 tempo workout”
- “Look at my current fitness and build a plan for the Fondo in September”
- “How's my form trending into next month?”
- “Break down my last interval session lap by lap”
Using a different client?
Any OAuth-capable MCP client connects the same way — paste the URL, sign in, approve.
stdio-only clients (or a local desktop config) can bridge with mcp-remote, which opens a browser for the same sign-in:npx mcp-remote https://rideindex.app/api/mcp
A client that can't do an OAuth handshake at all (an SDK-built agent, say) can use a personal access token as a static Authorization: Bearer … header instead.
Why it works this way
We don't run a model over your rides. You connect an assistant you already have, it reads your data on your instruction, and you can disconnect it at any time from your settings.
That means your training data isn't being handed to an AI vendor by us, and you're not paying us to resell you someone else's model.