Skip to main content
Illustration showing Migma connected to Grok Bot through the Migma Remote MCP URL

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.
This guide covers the Grok Bot desktop app.

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

If Migma appears under Settings → Plugins, add or enable it there, then continue to access approval. Until the listing is verified, create a Bot and paste this setup request:
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

Grok Bot opens a browser for access approval. Sign in yourself if needed. Verify the app, return destination, and every requested permission before selecting Allow.email:send allows test and direct sends. campaign:write allows campaign creation, send, and schedule. Select access that matches the work you want Grok Bot to perform.
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 and returns the connection credential through browser OAuth.
3

Verify with a read-only request

Ask:
A successful result should use migma_list_projects, return accessible brands, and leave Migma data unchanged.
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

If OAuth cannot complete

Some Grok Bot builds use an OAuth callback that Migma cannot accept. If Grok shows redirect_uris must be HTTPS:
  1. Ask Grok Bot to read https://api.migma.ai/auth.md.
  2. Confirm Grok can store the claim token and returned credential in its supported secret store.
  3. Open the claim link yourself, confirm the signed-in Migma account and requested scopes, then approve.
  4. Repeat the read-only brand request.
Claim-code returns a credential once for direct authenticated requests. Confirm secure storage and a durable connected state before completing setup.
campaign:write includes campaign creation, send, and schedule. For email-draft work, request email:read email:write.

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 a safe 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 or start with a managed Migma address before preparing the campaign.
8

Prepare the campaign for review

Migma needs campaign:write to create a campaign draft. This permission also includes send and schedule. 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

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

MCP permissions

Review access, approval, and revocation before connecting.

Migma MCP server

See hosted MCP behavior and troubleshooting.