Grok Bot + AgentMail

Give Grok Bot its own inbox

AgentMail is the best way to give Grok Bot its own inbox. Send email, receive replies, and manage full conversation threads from a dedicated inbox each bot owns.

Start for free Docs

[ Install ]

One command

Settings → Plugins → search AgentMail → Install → click Allow on the OAuth screen. 24 tools appear. Every bot on your account can call them. Same MCP server serves Grok Bot, Grok Build, and the Grok API.

Configure (credentials, email channel, verification)

[ Why email ]

Why your Grok Bot agent needs its own inbox

One address per bot

Not one connection shared across the fleet. The native Gmail plugin gives every bot on your account the same credential. AgentMail gives each bot a real address it owns.

Real inbound

The Gmail plugin lets your bot read your inbox. AgentMail lets people, or systems, email the bot directly, with full thread history and reply_to_message.

Scoped blast radius

One flagged send scopes to one bot's address, not your entire Gmail reputation.

[ Code ]

Working code

[ Recipes ]

Recipes

Copy any prompt into a Grok Bot chat. The tools listed are the ones the agent will call, so approve them when prompted.

Support

Process inbound

Watch an inbox, reply to what you can answer, forward the rest.

System Prompt

Prompt

Create an inbox called help-desk. Every 10 minutes, list unread messages. Reply to any question you can answer confidently. Forward the rest to support@mycompany.com. Label the ones you replied to as auto-answered and the ones you forwarded as escalated.

Tools

create_inboxlist_messagesreply_to_messageforward_messageupdate_message

Productivity

Join conversations

CC the bot on a thread. It reads the history and participates.

System Prompt

Prompt

When someone CCs you on an email thread, read the full history, understand what’s being asked, and respond as a helpful assistant. If it’s scheduling, propose three time slots. If it’s a question you can answer, answer it. Otherwise say what you need to help further.

Tools

list_messagesget_threadreply_to_message

Pattern originally described by Atal Upadhyay as the chief of staff move.

Verification

Identify and authenticate

Bot signs up for tools using its own address. Receives 2FA codes and completes verification on its own.

System Prompt

Prompt

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

Tools

create_inboxlist_messagesget_thread

Productivity

Operations

Cross-team status collector. The bot chases the humans.

System Prompt

Prompt

Every Friday at 3 PM, send the weekly status template to each person in direct-reports.csv from an inbox called ops-tracker. If someone hasn’t replied by Monday 10 AM, send a nudge. Compile every reply into a summary and email it to me by Monday 5 PM.

Tools

create_inboxsend_messagelist_messagesget_thread

Support

Tier-one support agent that handles the volume so humans handle the exceptions.

System Prompt

Prompt

Watch the support@ inbox. For each new message, classify: billing question, bug report, feature request, or other. Reply to billing using our FAQ. File bug reports as GitHub issues in mycompany/product. Forward feature requests to product@mycompany.com. Reply to the rest with a holding message and label needs-human.

Tools

list_messagesget_threadreply_to_messageforward_messageupdate_message

Sales

Lead qualification and follow-up chase, no CRM plugin required.

System Prompt

Prompt

For every new inbound in the demo-requests inbox, look up the sender’s LinkedIn, qualify against these criteria (SaaS company, 50+ employees, US-based). If qualified, reply with three meeting time options. If not, reply with our self-serve onboarding link. Log the outcome to qualification-log.csv.

Tools

list_messagesget_threadreply_to_messagecreate_draft

Recruiting

Candidate outreach and interview scheduling on autopilot.

System Prompt

Prompt

Reach out to the 60 candidates in sourced-candidates.csv from a new inbox called recruiting. Personalize each message referencing their most recent role. When someone replies with interest, propose three interview slots that work for me. When they pick one, send calendar invites. Update pipeline.csv with the status.

Tools

create_inboxsend_messagelist_messagesget_threadreply_to_messagecreate_draft

[ FAQ ]

FAQ

Common questions about AgentMail and Grok Bot.

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.

No. Grok Bot is only included with Cursor Ultra ($200/mo), SuperGrok Heavy ($300/mo), and Cursor Premium Teams ($120/seat/mo). SuperGrok Plus does not include Grok Bot. See x.ai/bot.

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.

Give your Grok Bot agent its own inbox

Free tier. No credit card required. Inboxes ready in under a second.

Start for free

All systems onlineSOC 2 Compliant

Email Inboxes for AI Agents

support@agentmail.cc

Newsletter

Subscribe to our weekly newsletter.

Navigation

Home Build Enterprise Agent Armor Pricing Blog Customers Compare Careers Docs Console

Social

Privacy PolicyTerms of ServiceSOC 2Subprocessors

Give Grok Bot its own inbox

One command

Why your Grok Bot agent needs its own inbox

One address per bot

Real inbound

Scoped blast radius

Working code

Recipes

Process inbound

Join conversations

Identify and authenticate

Operations

Support

Sales

Recruiting

FAQ

Is there an official email plugin for Grok Bot?

How do I give my Grok Bot its own email address?

How does this compare to the native Gmail plugin?

Does this work with SuperGrok Plus?

What is the difference between Grok Bot and Grok Build?

Do routines keep running when I close my laptop?

Where do I put the AgentMail API key?

Is it safe to let a Grok Bot read email?

Can I use my own domain?

What if I need push notifications instead of polling?

What if a send goes through cleanly but never lands?

Does this work with the Grok API directly?

How much does AgentMail cost?

Is AgentMail an official xAI plugin?

Give your Grok Bot agent its own inbox