Connect NexRex to Grok Bot: give your AI assistant real training context
Paste the NexRex MCP URL into Grok Bot, approve OAuth, and query real training context—AI drafts; you decide.
Generic training plans miss what makes your athletes tick. They don't know that Sarah ran a breakthrough 10K last month, that Marcus is recovering from IT band inflammation, or that Emily's wedding is in three weeks. Generic advice is safe—and safely mediocre.
The Model Context Protocol (MCP) changes that. Connect NexRex to Grok Bot, and your AI assistant gains read access to real training context: recent workouts, injury notes, race schedules, recovery trends, and your own coaching observations. It can draft workout adjustments or check-in messages grounded in what's actually happening—then you review, edit, and decide whether to send.
What MCP gives you
When you connect NexRex via MCP, Grok Bot can:
- Read athlete profiles: goals, training history, injury notes, race schedules
- Query recent workouts: completed runs, adherence patterns, training load trends
- Access recovery metrics: HRV, sleep scores, subjective feedback
- Review your observations: notes you've added, recent check-ins, communication history
- Draft contextual messages: check-ins, workout adjustments, race prep notes—based on real data, not generic templates
MCP is read-and-draft only. The AI assistant cannot save plans, send messages, or update athlete records. Every action requires your explicit approval. You stay in control.
How to connect
Connecting NexRex to Grok Bot takes less than a minute:
Step 1: Paste the MCP URL
In Grok Bot chat, paste the NexRex MCP server URL:
https://mcp.nexrex.ai/mcp
Grok Bot will recognize the URL and prompt you to add the server.
Step 2: Approve OAuth
Click Connect in Grok Bot. A browser window opens to:
app.nexrex.ai/mcp/connect
Log in to your NexRex account (if you're not already) and click Allow access. This grants Grok Bot read-only access to your coaching data via MCP.
Step 3: Verify the connection
Back in Grok Bot, you'll see a confirmation that the NexRex MCP server is connected. Try a query:
"Show me athletes who missed workouts this week"
"Draft a check-in for Sarah based on her recent HRV trend"
"What's Marcus's training status?"
If the query returns athlete-specific context, the connection is live.
What about Settings → Integrations?
You may have seen Settings → Integrations → MCP Server in the NexRex console. That section is for manual token management—API keys you generate for tools like Codex, custom scripts, or self-hosted MCP servers.
Do not use manual tokens for Grok Bot. The OAuth flow handles authentication automatically and scopes permissions correctly. Manual tokens require you to manage Bearer headers and refresh cycles yourself—unnecessary complexity for the Grok Bot integration.
Example prompts
Once connected, you can ask Grok Bot to:
- "List athletes with declining HRV over the past 7 days" — factual query, no draft
- "Draft a check-in message for Sarah addressing her missed workouts and low sleep scores" — draft based on real context
- "What races are coming up in the next 4 weeks?" — calendar query
- "Compare Marcus's current training load to his 4-week average" — analytical query
- "Propose three workout options for Emily's taper week" — draft suggestions
The AI assistant returns data or drafts. You review, adjust, and decide.
Safety boundaries
MCP access is scoped to coaching workflows. The AI assistant cannot:
- Diagnose injuries or medical conditions
- Clear athletes for return-to-play (RTP)
- Make unilateral training decisions
- Send messages or save plans without your approval
NexRex is an AI assistant, not an AI coach. The final call is always yours.
Resources
About this workflow: The NexRex MCP server is in Beta. OAuth-based connections are stable; the underlying data schema and query semantics may evolve. Documented breaking changes will be announced in the Changelog.
If you encounter issues or have feedback on the MCP integration, reach out via Contact Us or the in-app support channel.