Grok Bot is xAI's always-on agent. Each Bot works on its own cloud computer, so it can keep going on a task while you are away. This guide adds freddy to your Bot as a custom MCP server, using a message in chat. It is not for the Grok chat at grok.com (see Connect freddy to Grok) or for the Grok Build terminal agent.
Before you start
You need a freddy account, at least one connected source, and Grok Bot. To ask about your data right away, connect a source in freddy first. See Choose and connect a data source.
1. Ask your Bot to add freddy
You add freddy by asking your Bot in chat. Open a chat and send:
“Add a custom MCP server named freddy at https://freddy.coach/mcp”
Say “custom MCP server”, so your Bot adds freddy's address and does not look for a catalog plugin. The URL is the same for every freddy account. It contains no personal token. Use exactly https://freddy.coach/mcp, without adding anything to the path.
2. Confirm when it asks
Your Bot repeats the name and the URL and asks you to confirm. Check that the URL reads https://freddy.coach/mcp, then confirm.
3. Sign in to freddy
When your Bot shows the authorization step, follow it. freddy's authorization page opens in your browser. Sign in with your freddy email code if needed. Review any required Terms, Privacy and Consumer Health Data consent, then approve your Bot's access.
Enter your sign-in code on freddy's page, never in the chat. freddy uses OAuth for this connection. You do not need to give your Bot a freddy API key or access token. Grok Bot keeps the sign-in on its own servers and does not store it on the Bot's computer.
4. Ask about your data
Mention freddy in a chat and ask: “What data is available in my freddy account?” Your Bot can then use freddy's tools to find your connected metrics and read them for you. Try “How did I sleep last night?” or “Show me my last five runs.”
Manage access
You can remove the freddy server from your account's connected servers in Grok Bot. You can also revoke your Bot's access in freddy under Connected AI. Revoking it stops your Bot's access at once.
If you use Grok Bot on a team, your admin's connector policy can block custom servers. Ask your admin to allow freddy.coach.
If setup does not work
Check that your Bot has the exact URL https://freddy.coach/mcp and that it is using OAuth. Your Bot reaches the server over the public internet, so a typo in the URL is the most common cause. Do not paste an API key, MCP key or email code into the chat. If the sign-in still fails, contact freddy support with the error text, without sending a code or token.