Give Grok Bot its own inbox

Yes. AgentMail is in Grok Bot’s plugin browser under the AgentMail account. Install with one click, approve the OAuth prompt, and every bot has 24 email tools. Also works on Grok Build via grok mcp add.

Install the AgentMail plugin, then in a bot chat say "create an inbox called X". The bot uses create_inbox and returns a real address at X@yourworkspace.agentmail.to. That inbox now belongs to the bot: it can send from it, receive at it, and reply within threads.

The Gmail plugin gives your fleet one shared connection to your inbox. Every bot writes as you and can read anything in your Gmail. AgentMail gives each bot its own address. Multiple bots can operate independently with their own reputations, threading, and reply flows.

Yes. Grok Bot is included with SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard and Premium. See x.ai/bot for the current list.

Grok Bot is the always-on UI teammate (macOS, Windows, iOS). Grok Build is the CLI coding agent. Same MCP server, same 24 tools. Tool names are unprefixed in Grok Bot (send_message) and prefixed in Grok Build (agentmail__send_message). Auth differs too: Grok Bot uses OAuth, Grok Build uses Authorization: Bearer.

For Grok Bot, yes. Routines run on the bot’s persistent cloud computer. For Grok Build, no. It’s a terminal session that ends when you close it.

Grok Bot’s official plugin doesn’t need one, it uses OAuth. For Grok Build, grok mcp add writes the key to ~/.grok/config.toml. For the custom MCP connector fallback on Grok Bot, paste it as the x-api-key header value.

Every AgentMail inbox is scoped to the API key you configured. A bot with the plugin can read only inboxes it (or another bot on your account) has created. The Gmail plugin, by contrast, gives every bot access to your entire personal Gmail history. AgentMail’s blast radius is per-inbox.

Yes, on paid plans. Add your domain in the AgentMail console, verify DNS, and the bot can create addresses at agent@yourdomain.com. Every recipe on this page works with a branded domain.

Grok Bot’s routine triggers currently support Slack, GitHub, and Teams events, not email. Two workarounds: a scheduled routine that polls list_messages for unread every N minutes, or register an AgentMail webhook that posts to a Slack channel your bot has connected.

Check the AgentMail Console suppression list. Any address that ever bounced, complained, or unsubscribed is on your SES suppression list and future sends fail silently. Always test the first send to an external address.

Yes. Register https://mcp.agentmail.to/mcp as a remote MCP server in your Grok API tool array. Bearer auth via the authorization parameter. Full guide in the AgentMail MCP docs.

Free tier is enough to run every recipe on this page. Paid plans start when you need a custom domain, higher volume, or enterprise features.

It’s listed in the plugin browser Grok Bot ships with, alongside the other official plugins. AgentMail is an independent company; the marketplace listing is the extent of the xAI relationship.