Skip to main content
Connect Migma to Grok Bot to create editable emails using your saved brand, review previews, prepare campaigns for opted-in subscribers, and read results. Start with one draft. Creating an email does not send it. This guide covers the Grok Bot desktop app. You need a Migma account, access to your brand, and permission to add connections in Grok Bot.

Quick start

  1. Paste the setup prompt below into Grok Bot and approve the connection in your browser.
  2. Ask Grok Bot to find your brand read-only. Confirm that the returned brand is yours.
  3. Request one editable email draft. Open its preview and Migma canvas link before continuing.
For first-email prompts, read Grok Bot email marketing: setup and first draft. For audience, sender, review, and results, use Grok Bot email campaigns: from brief to results. Grok Bot connects through Migma Remote MCP, which lets it use Migma tools, at https://migma.ai/mcp. Sign-in and access approval happen in your browser.
Agent-guided Remote MCP setup is available in Grok Bot desktop with user approval. Marketplace availability and connector authentication vary by Grok build and workspace policy.
Use one write path per task. Finish or pause current work before switching between Migma MCP and browser operation. This prevents duplicate drafts.

Start email marketing with Grok Bot

Copy this prompt into Grok Bot:
Illustration showing Migma connected to Grok Bot through the Migma Remote MCP URL

Illustration of Migma connecting to Grok Bot through Remote MCP

Before you start

You need:
  • A Migma account.
  • Grok Bot desktop with plugins and MCP connections allowed.
  • A browser for Migma access approval.
Team and Enterprise admins may need to allow the Migma server URL before members can connect it. Grok Bot follows the same plugin and MCP policy as Cursor.

Connect Migma from Grok Bot

1

Ask Grok Bot to add Migma

Check Plugins → Your plugins for an existing Migma connection first. If it needs authentication, select Authenticate and complete the access approval. If no connection exists, create a Bot and paste the prompt above to add Migma.Grok Bot should discover https://migma.ai/mcp and ask before adding it. Choose the approval action only when the endpoint is exact.
Illustration showing Grok Bot reading Migma setup guidance, finding the Migma Remote MCP URL, and asking whether to add the connector

Illustration of Grok Bot discovering Migma Remote MCP and asking before adding it

2

Review Migma access

Follow the installed connector’s browser approval. Sign in if needed, review the app and permissions, then select Allow when they match your intended access. Return to Grok Bot and check the connector status.Full access lets Grok Bot design, import audiences, and send for you. Review those permissions before approval. Require confirmation for each send in the chat and keep Grok Bot’s approval controls enabled.
Illustration showing the Migma connection review with app, return destination, requested access, Cancel, and Allow

Illustration of the Migma access review opened by Grok Bot

Migma creates the connection credential after your approval and hands it to Grok Bot directly.
3

See your account

A Connected badge is the first check. Ask Grok Bot to make a read-only request for the brand you want to use:
Illustration showing Grok Bot calling Migma list projects, returning a sanitized demo brand, and making no changes

Illustration of Grok Bot verifying Migma with a read-only brand request

How Grok Bot connects

Use the installed Migma connector’s browser authentication first. In a September 4, 2026 check, selecting Authenticate restored an existing connector to Connected, and Grok Bot successfully read a Migma brand through its tools. This verifies that connection, not every Grok build or workspace policy. If a direct agent cannot complete browser OAuth, it may use the conditional claim-code flow described in Agent registration. That requires secure credential storage and does not repair a hosted connector that still reports needsAuth.

Create your first email draft

After the read-only request succeeds, replace the brackets and send:
Open the returned email and check the facts, branding, images, and links. For a focused change, identify that email by its canvas link and name the section to edit. Review the new preview before preparing recipients or delivery. Use Email Preflight to check the finished email. A test email is a separate send that requires your approval; it uses Migma’s sender and does not verify your own campaign sender.
Our September 4, 2026 Grok Bot check verified authentication and reading a saved brand. Draft generation reached the account’s daily limit, so that run did not verify a generated preview, edit, or received test. The workflow below describes documented Migma capabilities.

Other Grok clients

Grok web and Grok Build are separate from Grok Bot desktop. For Grok web, open grok.com/connectors, choose New Connector → Custom, and add https://migma.ai/mcp. For Grok Build:

Browser fallback

When you choose browser fallback, Grok Bot may operate a signed-in Migma browser session. Take over for password, passkey, two-factor code, and CAPTCHA. Every Bot shares that cloud computer and its browser sessions. Sign out after use.

Give Grok Bot its job

Ask Grok Bot to read this page, then save this operating instruction:

Run the email marketing loop

Migma MCP returns exact brand, email, campaign, audience, and result data. Use Migma tools as the active write path for this workflow.
1

Choose one brand

Ask Grok Bot to list Migma brands, then select one.
2

Save lasting brand facts

When you share tone, offers, product facts, policies, or FAQs that should persist, ask Migma to save them to the selected brand’s knowledge base.
3

Build a source brief

For current launches or product news, make Grok research primary sources first. Require a dated checklist of exact facts for each email and up to five public HTTPS source-image URLs. Use primary sources for facts and images for visual direction.
4

Create drafts first

Ask for one email or a short series. State audience, goal, approved facts, and CTA. End with Keep these as editable drafts and show every preview.
Illustration showing three Migma draft email previews in Grok Bot and confirmation that no email was sent

Illustration of Grok Bot returning three Migma drafts

5

Review and check

Review returned previews in Grok Bot. Check every required fact in content and every expected source asset in images before saying the work is complete. If a preview cannot be inspected, say verification is incomplete and open its Migma link. Ask for targeted text edits, then run compatibility and deliverability checks. Use replacement generation to add missing structured images.
6

Prepare the audience

Import only opted-in contacts, or choose an existing list or segment. Ask Grok Bot to report created, updated, skipped, and failed counts before continuing.
7

Confirm the sender

Ask Migma to list available sending domains and From addresses. If none are ready, set up a domain you own. A managed Migma address supports testing and small transactional sends, with a 50-email daily limit and a 50-recipient limit per send. Connect your own domain for larger campaigns.
8

Prepare the campaign for review

Ask Grok Bot to create the draft, then pause for review:
Illustration showing Grok Bot and Migma preparing a campaign summary with audience, sender, schedule, previews, and nothing sent

Illustration of a campaign waiting for approval

9

Approve the exact send

Send or schedule only after audience, recipient count, sender, subject, timing, and preview match your intent. Keep Grok Bot approval controls enabled.
10

Read results and improve the next brief

After sending, ask Migma for campaign stats and delivery logs. Use clicks, bounces, and complaints to shape the next draft.
Illustration showing Grok Bot using Migma campaign stats to summarize delivery, opens, clicks, bounces, and recommend the next brief

Illustration of Grok Bot reading campaign results through Migma

Prompts worth saving

Save an email you like

Grok Bot calls migma_save_reference with the selected emailId. This favorites the email and makes its saved design available to future emails for the same brand by default, unless saved references are disabled. Later edits to the favorite update the reference too. For a series, name the email you want to save. Grok Bot should use that email’s ID, confirm only after favorite: true, and continue your task. Saving requires project:write and does not need an HTML export, a new draft, or sending permission. Repeating the same emailId keeps it favorited.

Import an opted-in CSV

Approve one exact send

Read performance

Safe routines

After the Migma connection is verified, first run the task once. When the result is stable, save it as a Grok Bot skill or routine. Good routines prepare work and stop:
Keep routines in preparation and review mode. xAI recommends approval for sending, publishing, deleting, purchasing, and production changes.

Disconnect or revoke access

  1. Pause any routine that uses Migma.
  2. Open Settings → Plugins, find the installed Migma connector, and disconnect or remove it.
  3. Revoke its matching OAuth-created key in Migma Settings → Developers → API Keys.
  4. If you used claim-code, revoke the matching Agent: key and remove its stored credential from Grok.
  5. If you used browser fallback, sign out of Migma inside Grok Bot’s Computer.

Troubleshooting

Current Grok behavior: Grok Bot overview, get started and computer login, skills and routines, approvals and security, and Grok Build MCP.

Next

Grok Bot email campaign guide

Turn a brief into reviewed emails, prepare recipients, and read campaign results.

Grok Bot email prompts

Start with welcome, newsletter, and product-launch drafts.

MCP permissions

Review access, approval, and revocation before connecting.

Migma MCP server

See hosted MCP behavior and troubleshooting.
Last modified on September 30, 2026