Coach from
any assistant.
Connect Claude, ChatGPT or Cursor to your coach workspace — add clients, build programs, assign workouts and review every athlete without leaving the conversation.
OAuth sign-in · workspace-scoped · writes need your OK
Setup
Connect your assistant
Pick your platform — same steps as in your Diby account. Copy the server URL, add the connector, then sign in and approve access.
Connect an assistant
Add Diby as a connector in your assistant, then sign in with your Diby account. Enable MCP under Settings in your Diby account first.
Copy the server URL
https://mcp.diby.ioAdd it in Claude
In Claude, open Settings → Connectors → Add custom connector and paste the server URL. Works on web, desktop and mobile.
Sign in and approve
Your assistant opens the Diby sign-in — log in with your account and approve access to your coach workspace.
Why MCP
Your workspace, in the tools you already use.
Once connected, your assistant operates on live Diby data with the same permissions as your Diby account — for any client in your workspace.
- One coach workspace per connection
- Same permissions as your coach dashboard
- Operate any client without switching apps
- Writes preview first — you approve before save
Your assistants
Live Diby workspace
Same permissions as your coach dashboard — any client, any time.
Add & search clients
Build workouts & programs
Create exercises & assign plans
Schedule sessions & events
Draft messages to clients
Billing, stats & subscriptions
Full workspace
Run the platform from the chat.
MCP is not a read-only dashboard — it is your coaching workspace. Add clients, create exercises, build workouts and training programs, assign plans, schedule sessions, and review billing without opening Diby.
- Search clients and pull check-ins, goals and injuries
- Draft workouts and programs, then assign when you approve
- Schedule calendar events and training sessions
- Inspect subscriptions, invoices and revenue summaries
No workflow reset
Keep Claude. Keep ChatGPT. Keep coaching.
If you have already used MCP with another platform, the pattern is the same — connect, sign in, ask. You do not rebuild your setup; you plug Diby into the assistant you already open every day.
- Same connector flow as Claude, ChatGPT or Cursor MCP
- Enable once under Settings → MCP in your account
- Your clients stay on the Diby app — no change for them
- You pull live data whenever the conversation needs it
Web, desktop or mobile — connect once, coach from the thread.
Cursor works the same way — add the connector, sign in, ask.
Client intelligence
Every client, analyzed in one thread.
Pull check-ins, session execution, PRs, nutrition plans and workspace stats into a single conversation — so you can review anyone in depth before you write or assign anything.
“Who hasn't trained in two weeks — and what did they last log?”
“Compare Alex's squat progression over the last eight sessions.”
“Summarize Mia's check-ins, active program and upcoming calendar this month.”
- Dormant clients and workspace-wide stats
- Set-by-set session history and PRs
- Check-ins, goals and injury notes
- Nutrition plans and upcoming calendar
Example prompts
Ask like you would a staff member.
“Add a new client named Jordan and set their timezone to Lisbon.”
“Draft a 4-day hypertrophy program for Alex — show me the preview before saving.”
“Assign Thursday's lower-body workout to Mia and schedule a check-in message.”
MCP FAQ
MCP questions, answered.
A secure connector that plugs your Diby coach workspace into MCP-compatible assistants — Claude, ChatGPT, Cursor and others. Your assistant reads and acts on live coaching data with the same permissions as your Diby account.
Nearly everything you do on Diby: search and add clients, browse and build workouts and training programs, create exercises, assign plans, schedule sessions and calendar events, review check-ins and goals, pull nutrition plans, and inspect billing. Reads are instant; writes go through draft → preview → approve before anything is saved.
No. MCP is for you, the coach. Your clients keep training in the Diby app — logging sessions, following programs, and checking in as usual. You operate from your assistant; they stay on Diby.
Yes. Ask for workspace stats, dormant clients, a client's check-in history, PRs, session execution detail, or exercise progression — your assistant pulls live data so you can review anyone without opening Diby.
Yes. Connections use OAuth sign-in, run under your user account, and respect workspace RLS — an assistant only sees what you can see. Writes require your explicit approval before anything is saved.
Claude (web and desktop), ChatGPT connectors, Cursor, Claude Code, OpenClaw and Hermes. Settings → MCP in your Diby account walks you through the setup for each one.
No. Read tools fetch live data. Write tools use a draft → preview → approve → commit flow — nothing is saved until you confirm the preview in the conversation.
Connect Diby to your assistant
Start free, enable MCP in Settings, and coach from Claude, ChatGPT or Cursor.