Plug your AI.
What it is.
MCP (Model Context Protocol) is the standard socket between an AI assistant and a data source. Kimbia is one: you bring your own assistant, it queries your activities where they live. This is not a chatbot inside Kimbia - it is your agent, on your data.
Connect.
One address to hand your client, over HTTP transport:
Claude Code
One line in your terminal, available in every project afterwards.
claude mcp add --transport http kimbia https://kimbia.app/mcpClaude (desktop & web)
Settings → Connectors → Add custom connector, then paste the address.
https://kimbia.app/mcpOther clients
Any client that speaks MCP over streamable HTTP works. Pick that transport and paste the address.
https://kimbia.app/mcpOn the first call your browser opens a Kimbia page: sign in with your atproto handle, approve, done. No password, no token to copy around.
What the agent can read.
- Activities, laps, gear
- Every session as your watch recorded it, down to the lap and the split, plus what you noted after it (RPE, feeling, carbs, water...) - with filters, sorting and aggregates, so the agent can answer without pulling everything.
- Physiological profile
- HR zones, VDOT / VMA, FTP, weight, target paces, reference performances. The agent prescribes off your real numbers instead of guessing them from past runs.
- Plans and objectives
- Planned sessions and target races, so a week reads inside its cycle rather than on its own.
- Life events
- Travel, illness, injury, work, camps, so the agent reads a gap in your training for what it was.
Tell your agent to start with the kimbia_mcp_describe tool: it returns who you are, the athletes it is allowed to query with their units, and a guide for each tool.
Reads, and writes your calendar.
The agent reads. The one place it may write is your calendar - sessions, objectives, life events - and only what an agent wrote: anything you edit in the app becomes yours, and the agent can no longer change or remove it. Activities, benchmarks and gear stay yours to edit, in the app. Off by default: a session feedback tool you can enable in Settings → AI - linked to your account, while what it says stays anonymized.
Coach and athlete.
A coach only sees an athlete's data while the athlete has opened an access window from their Crew page - from 1 hour to 1 year, revocable in one click. With no open window, the athlete is simply invisible to the coach's MCP.
Revoke.
Every connected client is listed in Settings → AI, with its last use. One click on “Revoke” cuts its access immediately.
My connected clients