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

AgentMail is the first email provider built for AI agents.

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

[ Templates ]

Templates

Live Grok bots, each running on its own AgentMail inbox. Open one to add it to your account and email it.

Sales

Lead

Qualifies inbound demo email. Replies with times or a self-serve link.

Open →

Support

Desk

Tier-one support inbox. Answers from your FAQ, escalates the rest.

Open →

Productivity

Threadmate

CC it on a thread. Reads the history and replies from your brief.

Open →

Productivity

Scheduler

Negotiates meeting times over email until everyone agrees.

Open →

Productivity

Forward

Forward any email with a one-line instruction. It acts or drafts back.

Open →

Operations

Chaser

Nudges people for outstanding docs and files what comes back.

Open →

Sales

Replies

Classifies outbound replies and drafts the next touch or escalates.

Open →

Recruiting

Recruiter

Candidate outreach from its own inbox. Proposes interview slots.

Open →

Operations

Approval

Human-in-the-loop send gate. A yes reply releases the email.

Open →

Operations

Chief

One public email front door. Routes work across your bot fleet.

Open →

Content

Shakespeare

Drafts blog and use-case pages, audits live ones, refreshes the queue.

Open →

Sales

Outbound

Scores accounts, drafts sequences, enrolls sends, handles replies.

Open →

[ Builder ]

Looking for inspiration?

Jam with our agent builder. Describe what you want and it gives you a working template in seconds, with the exact instructions to hand your agent.

Open the builder

[ 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.

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.

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 Pricing Blog Customers Compare Use cases Careers Docs Console AgentID Agent Armor

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

Templates

Lead

Desk

Threadmate

Scheduler

Forward

Chaser

Replies

Recruiter

Approval

Chief

Shakespeare

Outbound

Looking for inspiration?

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