Build. Demo. Win. $500

Join

GROK BOT

Give Grok Bot
its own inbox.

Connect Mermail as a custom OAuth MCP connector for persistent email workflows.

Why Grok Bot

Built for the agent you already use.

Mermail gives Grok Bot a dedicated inbox and payment layer so verification, checkout, and receipts stay in the same loop.

Dedicated mailboxes instead of a shared personal Gmail login
Real inbound email with full thread context
OAuth-scoped access to one Mermail workspace
Persistent Bot routines can poll and handle new mail

Before you start

Check 3 things.

A Grok account with Connectors access.

For a managed team, an admin has provisioned the custom connector.

You can sign in to the intended Mermail workspace.

Grok connector docs

Success contract

Done when all 3 pass.

Mermail appears as a connected tool in Grok Bot.

list_mailboxes succeeds in a Bot chat.

The Bot can reuse a dedicated mailbox and inspect clean inbound mail.

Three steps to connect.

1

Copy the Mermail MCP URL

Use Streamable HTTP with OAuth. Add no headers.

MCP endpoint
https://console.mermail.app/mcp
2

Add a custom MCP connector

Open Grok Connectors, choose New Connector → Custom, and paste the URL.

Open Grok Connectors
3

Authorize, then verify

Finish OAuth, mention @Mermail in the Bot chat, then run the read-only check.

Verify
Ask: "List my Mermail mailboxes" (tool: list_mailboxes)

Questions, answered.

Fast fixes for auth, setup, and discovery.

Is Mermail an official Grok Bot plugin?+

No. Add it as a custom MCP connector; Grok discovers the hosted Mermail tools through OAuth.

Does Grok Bot need a Mermail API key?+

No. Use OAuth and add no custom headers. This keeps PayBox and x402 tools available.

Does each Bot get a separate email address?+

Bots share the connector, but each can reuse a dedicated Mermail mailbox for its own identity and threads.

Can a Grok Bot routine watch for new email?+

Yes. Schedule a routine to poll list_emails; email is not currently a native Grok Bot event trigger.