Connect your email to Grok Bot (and Grok): inbox and calendar over MCP
Grok Bot — the new always-on cloud agent from xAI and Cursor — supports remote MCP servers, and so do the Grok app, Grok Build and the xAI API. Here is how to give them real access to your mailbox — any IMAP provider, iCloud, OVH, Zoho or your own domain — in about a minute.
Grok Bot is the most interesting thing to happen to personal agents this month: an always-on agent from xAI and Cursor that lives on a persistent cloud computer — its own browser, files and terminal — and keeps working through tasks and routines while your laptop is closed. An agent like that is only as useful as what it can reach, and the single most useful thing you can hand it is your inbox: morning digests, triage routines, drafted replies, chased threads — running on a schedule, unattended.
Grok Bot reaches outside tools over MCP — the same open protocol Claude, ChatGPT and Cursor use — and so does the rest of the Grok lineup: custom connectors in the Grok app, native MCP in the Grok Build CLI, and remote MCP tools in the xAI API. The catch is the same one every assistant has: built-in connectors cover the big OAuth platforms — Outlook, Google Workspace, Notion, GitHub, Linear. If your mail lives anywhere else — a domain at OVH or IONOS, an iCloud address, Zoho, Fastmail, or the cPanel box at your web host — there is no native connector, and there never will be one per provider. That is exactly the gap a custom MCP connector fills.
What a Grok agent can do with your mailbox
anymailmcp.com wraps any IMAP/SMTP mailbox (and its CalDAV calendar, when your provider has one) into one MCP URL. Connected, your mailbox becomes a set of tools the agent can call: search and read mail, draft and send replies, file and label messages, check your week and book events. Nothing is copied into a database — every read is a live IMAP call to your own mail server.
Connect it to Grok Bot
- In Grok Bot, open Settings → Plugins and choose Add custom connector. (Grok Bot ships with SuperGrok Plus/Heavy and Cursor Pro+/Ultra plans; team admins manage plugins from the dashboard.)
- Name it and paste
https://anymailmcp.com/mcpas the server URL. No auth headers needed — the sign-in that opens handles everything: enter your email, click the magic link we send you, and connect your mailbox with the same address and password you would type into Thunderbird. Settings are auto-detected and verified live against your mail server. - Your Bot's tasks and routines can now @-mention the mail and calendar tools like any other plugin.
Two notes specific to Grok Bot. First, it runs on a cloud computer, so it only reaches MCP servers on the public internet — local/stdio servers do not attach. anymailmcp.com is hosted, so there is nothing to tunnel. Second, its connector form has no field for a pre-registered OAuth client ID — it relies on the server supporting dynamic client registration, which we do; the flow just works.
Connect it to the Grok app (grok.com)
- Go to grok.com/connectors — connectors are available to all Grok users (on Business/Enterprise plans an admin provisions them).
- Click New Connector and choose Custom.
- Paste
https://anymailmcp.com/mcpas the server URL. - Complete the sign-in that opens: enter your email, click the magic link we send you, and connect your mailbox with the same address and password you would type into Thunderbird. Settings are auto-detected and verified live against your mail server.
Grok discovers the mail and calendar tools automatically and they show up in your next chat, exactly like the built-in connectors.
Connect it to Grok Build (the CLI)
Grok Build reads the same MCP configuration format as Claude Code — if you already use MCP servers there, the identical entry works with zero reconfiguration. Add to your .mcp.json:
{
"mcpServers": {
"anymail": {
"url": "https://anymailmcp.com/mcp"
}
}
}On first use, Grok Build opens the browser for the same one-minute sign-in, and your agent sessions can then search, triage and draft against your real inbox.
Connect it through the xAI API
Building on the API? xAI's remote MCP tools take a server URL in the request's tools array (Streamable HTTP and SSE transports). Point it at https://anymailmcp.com/mcp with an authorization token from your account and your application gets the same mail tools server-side.
Decide how much Grok is allowed to do
Access levels are set per mailbox, on our side, where the model cannot change them:
- Read: search, read and list only — briefings and summaries, zero risk.
- Read & organize: adds drafts, filing, flags and calendar events; no sending, no deletion. Grok prepares, you press send.
- Full: everything, including sending — for when it has earned it.
This matters double for Grok Bot: an always-on agent working unattended deserves read or read & organize until it has earned more — a misfiring routine can then waste a few calls, not email your clients. Credentials are AES-256-GCM encrypted and revocable in one click, daily quotas cap the blast radius, and where your provider offers app passwords the connect page steers you to one, so Grok's key is never your real password.
Try it now
Pick where your email is hosted below. The free tier covers one mailbox and every tool at 15 calls a day, no card required.
Which providers work?
Any provider that speaks IMAP: OVH, IONOS, iCloud, Zoho, Fastmail, Comcast, AOL and the rest of the providers page, each with its own walkthrough — plus any custom IMAP/SMTP server via advanced configuration, verified live at connect time.
Ready to let your assistant into your inbox?
Get started, free