Is AgentMail an official plugin for Grok Bot?

Yes. AgentMail is an official Cursor plugin, and Grok Bot ships with the Cursor plugin browser. Install with one click from Settings → Plugins.

Does this cost anything?

AgentMail's free tier covers everything in this post. Grok Bot itself requires Cursor Ultra ($200/mo), SuperGrok Heavy ($300/mo), or Cursor Premium Teams ($120/seat/mo). SuperGrok Plus does not include Grok Bot.

Can I use my own domain?

Yes, on paid plans. Add your domain in the AgentMail console, verify DNS, and the bot can create addresses at agent@yourdomain.com.

Do routines keep running when my laptop is closed?

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

What if a send goes through cleanly but never lands?

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 like Gmail.

Is it safe to let a bot read email?

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 created. The Gmail plugin, by contrast, gives every bot access to your entire personal Gmail history.

How to Give Your Grok Bot Its Own Email Address

How do I give my Grok Bot an email address?

Install the AgentMail plugin from the Grok Bot plugin browser, then click Allow on the OAuth screen. Every bot on your account gets 24 email tools: create_inbox, send_message, list_messages, reply_to_message, and 20 more. Each bot then owns a real email address at yourworkspace.agentmail.to that it can send from, receive at, and reply within threads. Total setup time is about three minutes. AgentMail is an official Cursor plugin in Grok Bot, so there is no manual API key entry.

TL;DR

AgentMail is an official Cursor plugin in Grok Bot. One-click install.
OAuth authorization, no API key to paste. Click Allow on the "Cursor wants to access AgentMail" screen. Grok Bot uses Cursor's plugin plumbing, so the prompt identifies as Cursor.
24 email tools per bot. Send, receive, reply, thread, forward, draft.
Each Grok Bot gets its own address. No sharing your Gmail across the fleet.
Same plugin works on Grok Build via grok mcp add.

Elon Musk quote-tweeting the post about giving a Grok Bot its own email address, with the original post visible below it

Give your Grok Bot an email address with AgentMail. Elon Musk himself agrees.

Why give Grok Bot an email address?

Grok Bot ships with a Gmail plugin, but that plugin points at your inbox. Your outreach bot, your support bot, and your ops bot all end up writing as you, from the same address, with no way to separate them. Your outreach bot spams a prospect, your Gmail gets flagged, and your personal mail stops delivering. One bot's mistake takes the whole fleet down with your real reputation.

An address the bot owns fixes the shape. Each inbox is a real address with its own suppressions, its own sending reputation, and its own thread history. A bot can sign up for services in its own name, because the verification code lands somewhere that belongs to it. People can email the bot directly and it replies inside the same thread. A flagged send scopes to one bot's address instead of your entire Gmail.

How do I install AgentMail on Grok Bot?

You need a Grok Bot account (Cursor Ultra, SuperGrok Heavy, or Cursor Premium Teams) and an AgentMail account. AgentMail's free tier covers everything below.

1. Open Grok Bot. Go to Settings → Plugins. Search for AgentMail. Click Install.

The AgentMail plugin inside Grok Bot's Settings, Plugins panel, showing connected accounts, the enabled email tools, connectors, and skills

2. Approve the OAuth prompt. Your browser opens an AgentMail authorization screen. It says "Cursor wants to access AgentMail on behalf of you@yourdomain" because Grok Bot uses Cursor's plugin plumbing. Click Allow. No API key to paste.

The AgentMail OAuth authorization screen reading "Cursor wants to access AgentMail on behalf of", with Deny and Allow buttons

3. Check the connector card. 24 tools appear.

4. Create a bot with an email job. In the description, give it authority to run its own inbox. Example: "You are my outbound sales bot. Use AgentMail to create yourself an inbox called outreach. Send follow-ups from that inbox. Read replies daily."

5. Try it. Ask the bot to email you at your real address. The mail lands. Reply from your inbox. Ask the bot to check. It reads your reply in the same thread.

A Grok Bot chat where the bot creates its own AgentMail inbox, sends a test email, and confirms the send

Gmail showing the email delivered from the bot's own AgentMail address

What can my Grok Bot do with its own inbox?

Four things you cannot do with the built-in Gmail plugin.

Sign the bot up for its own accounts. Notion, Stripe, Vercel, anything with a signup form. The 2FA code lands in the bot's inbox. The bot reads it, pastes it, finishes signup. Nothing runs under your Google identity.

Run a real cold outreach loop. The bot sends from its own address, tracks each thread, drafts personalized replies. Your inbox stays clean. Deliverability does not compete with your personal mail. A flagged send scopes to one bot's address, not your entire Gmail.

Own a support inbox. help-desk@yourdomain belongs to the bot. It handles first-line replies, forwards the rest to a human. Same pattern as Zendesk AI at a fraction of the cost.

Put the bot in a group email thread. CC assistant@yourdomain on any thread. The bot reads the history, participates like a colleague, replies inside the thread. Atal Upadhyay wrote about this as the chief of staff move.

What are some example prompts?

Drop any of these into a bot after installing.

Sign up for accounts:

Sign up for a free Notion account using notion-bot@my-workspace.agentmail.to. When the verification code arrives, read it and finish signup. Report the account details.

Cold outreach with reply handling:

From a new inbox called outreach, send this pitch to every row in leads.csv. Personalize the greeting with the first_name column. When someone replies, draft a response and hold for my approval.

Auto-triage a founder inbox:

Create an inbox called founder@. Every 10 minutes, list unread. Reply to anything you can answer. Forward anything about legal, money, or contracts to me. Label the rest as later.

Meeting scheduler:

When someone emails meet@my-workspace.agentmail.to, read the thread, check my Google Calendar, and reply with three 30-minute slots that work in their timezone.

Why not just use the Gmail plugin?

The Gmail plugin is fine if you have one bot doing personal errands on your inbox. The moment you have two bots, the model breaks.

Every bot uses the same connection. Outbound from your outreach bot and outbound from your support bot both look like they came from you. No bot can own an address, so no bot can sign up for services in its own name. If your Gmail gets flagged for something one bot did, your personal mail goes down with it. There is no per-account permission, so you cannot tell one bot to work with the client mailbox and another to stay out of it.

AgentMail was built for the opposite shape. Each inbox is a real address the bot owns. Each bot can have as many as it needs. Suppressions, reputations, and thread histories scope per inbox.

Does this work with Grok Build?

Yes. Same MCP server, one command:

grok mcp add --transport http agentmail https://mcp.agentmail.to/mcp --header "Authorization: Bearer YOUR_API_KEY"

The Authorization: Bearer header is what Grok Build's MCP client expects. Same 24 tools in any Grok Build session. Tool names are prefixed on Grok Build (agentmail__create_inbox), otherwise identical.

AgentMail gives your agents real inboxes. Create inboxes via API. Send and receive Emails with 0 complexity. Free to start.

Get Started Read the Docs