How to Give Your Grok Bot Its Own Email Address
Connect Mermail to Grok Bot over MCP and every bot gets its own privacy-first email inbox — send, receive, reply, and sign up for services without sharing your Gmail.
By Toan Nhu
Mermail gives your AI agents a real, privacy-first email inbox. Connect it to Grok Bot over MCP, authorize once, and every bot on your account owns a real address it can send from, receive at, and reply within threads. A few minutes end to end.
How do I give my Grok Bot an email address?
Connect Mermail to Grok Bot through the Model Context Protocol (MCP), then authorize the connection. Every bot on your account gets a full set of email tools — create an inbox, send a message, list messages, reply in a thread, and more. Each bot then owns a real email address at your Mermail workspace (or your own verified custom domain) that it can send from, receive at, and reply within threads. Total setup time is about three minutes.
TL;DR
- Mermail connects over MCP. One MCP URL, one authorization, done.
- OAuth or API-key authorization, no API key to paste manually. The MCP flow handles auth for you.
- A full set of email tools per bot. Send, receive, reply, thread, draft, triage.
- Each Grok Bot gets its own address. No sharing your Gmail across the fleet.
- Same MCP server works in Grok Build and any other MCP-compatible assistant (Claude, Cursor, Codex, ChatGPT).
Give your Grok Bot an email address with Mermail.
On this page
- Why give Grok Bot an email address?
- How do I connect Mermail to Grok Bot?
- What can my Grok Bot do with its own inbox?
- What are some example prompts?
- Why not just use the Gmail plugin?
- Does this work with Grok Build?
Why give Grok Bot an email address?
Grok Bot ships with a Gmail connection, but that connection 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 — and, with Mermail's privacy-first design, you keep user-owned encrypted storage and explicit authorization over what your agent actually sends.
How do I connect Mermail to Grok Bot?
You need a Grok Bot account and a Mermail account. Mermail's free tier covers everything below.
1. Get your Mermail MCP URL. Log in to the Mermail console and grab the MCP endpoint. Use the agent-inbox profile URL for a focused set of email tools:
https://console.mermail.app/mcp?profile=agent-inbox2. Add Mermail as an MCP server in Grok Bot. Open Grok Bot, go to Settings → MCP (or integrations), and add the Mermail MCP URL. Authorize the connection — Mermail uses OAuth, so you sign in and pick a workspace. No raw API key to paste by hand.
3. Check the connector card. The email 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 Mermail 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.
What can my Grok Bot do with its own inbox?
Four things you cannot do with the built-in Gmail connection.
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 outbound 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. Because Mermail mailboxes are privacy-first with user-owned encrypted storage, your support data stays under your control.
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.
What are some example prompts?
Drop any of these into a bot after connecting Mermail.
Sign up for accounts:
Sign up for a free Notion account using [email protected]. When the verification code arrives, read it and finish signup. Report the account details.
Outbound 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 [email protected], 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 connection 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.
Mermail 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, thread histories, and encrypted storage scope per inbox — and email effects still require your explicit authorization.
Does this work with Grok Build?
Yes. Same MCP server, one command:
grok mcp add --transport http mermail https://console.mermail.app/mcp?profile=agent-inbox --header "Authorization: Bearer <your-api-key>"The Authorization: Bearer (or x-api-key) header is what Grok Build's MCP client expects. The same email tools appear in any Grok Build session. Tool names are prefixed on Grok Build (mermail__create_inbox), otherwise identical.
Mermail gives your agents real, privacy-first inboxes. Create inboxes via API, send and receive email with zero complexity, and add a user-controlled Agent Wallet for x402 payments when your agent needs to actually transact. Free to start.
FAQ
Does Mermail work with Grok Bot?
Yes. Mermail exposes a Model Context Protocol (MCP) server, and Grok Bot supports MCP connections. Add the Mermail MCP URL, authorize with OAuth, and every bot gets its own inbox.
Does this cost anything?
Mermail's free tier covers everything in this post. Grok Bot itself is included with the relevant xAI plans. See x.ai for current plans and pricing.
Can I use my own domain?
Yes, on Mermail's paid plans. Add your domain in the Mermail console, verify DNS, and the bot can create addresses at [email protected]. See the custom domains guide.
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 Mermail console suppression list. Any address that ever bounced, complained, or unsubscribed is on your 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 Mermail inbox is scoped to the workspace you authorized. A bot with the MCP connection can read only inboxes it or another bot on your account created — and email effects require your explicit authorization. The Gmail connection, by contrast, gives every bot access to your entire personal Gmail history.
