Connect Migma to Grok Bot through Remote MCP, approve access in your browser, and prepare branded emails, audiences, campaigns, and reports from chat.
Migma connects to Grok Bot through Remote MCP
Connect Migma once, then ask Grok Bot to design emails, prepare opted-in audiences and campaigns, and read results through Migma tools.Grok Bot works through Migma Remote MCP at https://migma.ai/mcp. Use the browser for sign-in, access review, and claim approval.
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.
Set up Migma so you can run my email marketing.Read https://docs.migma.ai/grok.md and connect with full access. I'll approve in my browser.Then show me my brands and suggest what we should do first.
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.
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 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 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:
Use Migma to find my brand [brand name] read-only.State which Migma tool succeeded. Do not create or send anything yet.
Illustration of Grok Bot verifying Migma with a read-only brand request
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.For a dated connection check and a draft-first workflow, see email marketing for Grok Bot with Migma.
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:
grok mcp add --transport http migma https://migma.ai/mcpgrok mcp doctor migma
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.
Ask Grok Bot to read this page, then save this operating instruction:
You run my communication through Migma: launches, announcements, newsletters, campaigns.Start each session with migma_get_context, read the setup block, and tell me the one next step.When something is missing, set it up in this order and offer one at a time: brand kit, design references, audience, sending domain, first email.Create drafts and show me every preview and canvas link.When I name an email or site as a design reference, pull the real screenshot, pass it as a reference image, and save it for next time.Build on facts from my brand or facts I give you, and send only to people who opted in.Before any send or schedule, show me the audience, recipient count, sender, subject, and final preview, then wait for my yes in this chat.
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.
Use Migma with brand [name].Create 3 launch emails for [audience].Goal: [action].Required facts by email: [exact checklist from verified sources].Source images: [up to 5 public HTTPS URLs].Pass those URLs through migma_generate_email.images as structured image inputs.Keep every email as an editable Migma draft and show each preview.
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 or start with a managed Migma address before preparing the campaign.
8
Prepare the campaign for review
Ask Grok Bot to create the draft, then pause for review:
Create a campaign draft from email [email id or canvas link].Recipients: [opted-in list or segment].Subject: [subject].Sender: [sender].Keep the campaign in draft. Show recipient count, sender, subject, and final preview, then wait for my approval.
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 of Grok Bot reading campaign results through Migma
Use Migma with brand [name].Import this CSV into a list named "[list name]".These contacts opted in on our site.Use one contact import with the full CSV text.Report created, updated, skipped, and failed counts.
Use campaign [name or id].Confirm the audience, recipient count, sender, subject, final preview, date, time, and timezone.Send when every value matches this conversation.When any value differs, show the exact correction and wait for approval.
Use Migma to show stats and recent delivery logs for campaign [name or id].Explain the strongest click signal, bounces, and complaints in plain language.Recommend the next email brief and return the analysis only.
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:
Every Monday at 9:00 AM, review last week's Migma campaign results for brand [name].Prepare one draft based on the strongest click signal.Use only approved brand facts and opted-in audience data.Show the preview and reasoning, then wait for approval.
Keep routines in preparation and review mode. xAI recommends approval for sending, publishing, deleting, purchasing, and production changes.
Check Settings → Plugins and workspace MCP policy. An admin may need to allow https://migma.ai/mcp.
Migma keeps asking for login
Open Plugins → Your plugins → Migma, select Authenticate, and complete browser approval. Then repeat a read-only brand request.
Bot cannot find a brand
Confirm the approved Migma account can access that brand, then repeat the read-only brand request.
Bot starts changing data during setup
Send Stop now, then repeat the setup prompt above.
Bot keeps retrying a connector OAuth flow
Stop the retry loop and inspect the installed connector. Complete its authentication, then verify with a read-only brand request. If it still fails, report the exact error and Grok build.
A direct agent needs a connection credential
Follow the conditional fallback in Agent registration. The agent must support secure credential storage; approve access in your browser.
Duplicate drafts appear
Browser and MCP wrote at the same time. Stop both, list existing drafts read-only, keep one set, then continue through one mode.
Researched features or images are missing
Rebuild an exact fact checklist. Pass source URLs through structured images, regenerate once, then verify content and previews.
Generation reports a daily limit
Check your Migma plan and usage. Wait for the limit to reset or review an upgrade yourself, then retry once. A successful connection does not mean generation capacity remains.
