How to Connect Grok Bot to Sequenzy with MCP

Grok Bot can work inside tools using connectors, MCP, and its persistent cloud computer. Connecting it to Sequenzy gives the Bot a structured email-marketing surface for campaigns, subscribers, segments, sequences, templates, analytics, and related workflows.

The connection is a custom remote MCP server, not a built-in Grok connector.

Grok Bot -> Sequenzy hosted MCP -> your authorized Sequenzy workspace

This guide uses the hosted endpoint and OAuth. It does not require a local process, Node.js, a tunnel, or an API key pasted into a conversation.

Before You Start

You need:

• Access to Grok Bot and its Plugins settings
• A Sequenzy account with access to the intended workspace
• Permission to add a connector; team policy may restrict MCP servers
• A browser available for the OAuth approval flow
• A low-risk test task

Grok Bot is a distinct product surface from Grok on the web, Grok Build, Grok Automations, and the xAI API. Their MCP configuration formats are not interchangeable.

The Sequenzy Remote MCP URL

Use this exact endpoint:

https://api.sequenzy.com/v1/mcp

It uses Streamable HTTP and browser-based OAuth. The same canonical URL is published in Sequenzy's MCP documentation and server metadata.

Step 1: Find the Connector Surface Your Account Exposes

In the Grok Bot desktop app:

1. Open Settings.
2. Open Plugins.
3. Check whether your account exposes a custom connector or MCP option.

xAI's Grok Bot setup documentation places supported connectors under Settings → Plugins. Separately, xAI documents adding a custom MCP URL through Grok connector settings. xAI does not currently document one universal Grok Bot screen for entering a custom URL.

If Grok Bot exposes the custom-URL control, continue there. If it only shows installed or marketplace plugins, register the connector through the Grok connector surface available to your account or ask a team administrator to provision and allow it. Grok Bot inherits the team's Cursor plugin and MCP policy.

Step 2: Add Sequenzy

Enter:

Name: Sequenzy
Server URL: https://api.sequenzy.com/v1/mcp

If the custom connector form requests a description, use:

Email marketing tools for managing campaigns, subscribers, segments,
sequences, templates, analytics, and transactional email.

Do not enter .grok/config.toml syntax or an xAI Responses API tools object here. Those belong to Grok Build and the xAI API respectively.

Step 3: Complete Sequenzy OAuth

After Grok opens the authorization flow:

1. Sign in to Sequenzy in the browser.
2. Confirm the Sequenzy account and workspace.
3. Review the requested access.
4. Approve only the permissions the Bot needs.
5. Return to Grok Bot and confirm the connector is authenticated.

Never paste your Sequenzy password, OAuth code, session cookie, or API key into a Bot message. Use the secure browser flow.

Step 4: Attach the Connector to the Bot

Grok Bot connectors are installed at the account level but can be enabled or referenced for a particular Bot. In the conversation, use the connector picker or type @ and select Sequenzy when available.

Create a focused Bot rather than a catch-all agent:

Name: Lifecycle operator
 
Job: Audit and improve our lifecycle email program in Sequenzy.
 
Instructions: Begin with read-only inspection. Preserve source IDs and links.
Never alter subscribers, campaigns, sequences, templates, schedules, or live
sends without showing me the proposed change and receiving explicit approval.
Treat suppression, consent, and transactional priority as hard constraints.

xAI's Grok Bot overview notes that a user's Bots share one cloud computer, including files and app sessions. Separate Bots are workflow boundaries, not security boundaries.

Step 5: Verify with Read-Only Requests

Start with a prompt that cannot send or modify anything:

Use @Sequenzy in read-only mode. Identify the connected account and workspace,
then list the five most recent campaigns and active sequences. Return names,
statuses, dates, and source IDs. Do not create, update, delete, schedule, or send.
Stop and report the exact error if any permission is missing.

Verify:

• The intended workspace is connected.
• The Bot returns current structured data rather than guessing.
• IDs and statuses match the Sequenzy dashboard.
• No change appears in the audit trail.
• Permission errors are explicit.

Then try a bounded analysis:

Review the last 30 days of campaign and sequence performance. Separate facts
from hypotheses. Identify three anomalies worth investigating, cite the data
behind each, and make no changes.

Step 6: Test a Draft Workflow

Move from inspection to a reversible draft:

Draft—not send—a lifecycle email for trial users who started setup but have not
reached activation after 24 hours. First show the proposed eligibility,
exclusions, success exit, metric, subject, preview text, and body outline.
Do not create the segment or sequence until I approve the plan.

After approving the plan, let the Bot create a draft. Inspect the audience logic, exit conditions, links, personalization fallbacks, and rendered test.

Step 7: Add Approval Boundaries

xAI's Grok Bot security guidance recommends stronger review for consequential external actions. Email deserves explicit boundaries because a wrong change can affect real people and sender reputation.

Require approval for:

• Adding, deleting, suppressing, or importing subscribers
• Changing consent, segments, or audience filters
• Activating or pausing a sequence
• Changing a live campaign or template
• Sending a test to anyone outside the approved test list
• Scheduling, rescheduling, or sending a campaign
• Changing domains, DNS, webhooks, integrations, or permissions

Allow read-only account, campaign, sequence, and analytics inspection first. Expand access when the workflow has earned it.

A Safe First Operating Prompt

You are my lifecycle email operator using @Sequenzy.
 
Operating rules:
1. Start every task by stating the workspace and whether the work is read-only,
   draft-only, or externally consequential.
2. Never infer consent, suppressions, customer state, or a missing metric.
3. Show eligibility, exclusions, priority, success exit, ineligibility exit,
   and measurement before proposing copy.
4. Draft first. Require my explicit approval before any write.
5. Require a second explicit approval before a test, activation, schedule, or send.
6. For sends, restate the final audience count, subject, sender, schedule,
   suppression state, and rollback or pause path.
7. Preserve exact tool errors and stop instead of improvising around permissions.

Troubleshooting

The connector is disabled

Check whether the account or team has disabled custom MCP servers, uses an allowlist, or requires administrator-installed plugins. Ask the administrator to approve the exact HTTPS endpoint.

OAuth does not finish

Keep Grok Bot open, return to the connector detail page, restart authentication, and make sure the browser is signed into the intended Sequenzy account. Do not copy tokens between windows.

The Bot sees the wrong workspace

Stop all write operations. Reopen the OAuth connection, inspect the authorized identity, and verify workspace access in Sequenzy before retrying the read-only account request.

The Bot can read but cannot write

This usually means the authorization does not include the requested scope or a safer access preset is active. Keep the exact error, decide whether the capability is genuinely required, and update permission through the proper connector or Sequenzy settings—never by giving the Bot a broader secret.

Tools do not appear in chat

Confirm the plugin is installed and authenticated, then enable it for the current Bot or attach it with @. Restart the app if the connector was installed while the conversation was open.

A task asks for .grok/config.toml

That file belongs to Grok Build. Return to Grok Bot's Plugins or MCP settings. Do not mix the two setup paths.

Grok Bot vs. Other Grok MCP Surfaces

This distinction matters when troubleshooting. A valid configuration for one surface can be meaningless in another.

FAQ

Does Sequenzy have a Grok Bot connector?

Sequenzy exposes a hosted custom MCP server compatible with connector-based MCP clients. Grok Bot can use it when the connector is available or provisioned for the account; it is not a built-in connector maintained by xAI.

What MCP URL should I use?

Use https://api.sequenzy.com/v1/mcp and complete OAuth in the browser.

Do I need Node.js or a local server?

No. The hosted connection needs neither a local npx process nor a tunnel.

Is Grok Build setup the same?

No. Grok Build uses its own CLI and config file. This page is for the Grok Bot app.

Should a Bot send campaigns automatically?

Begin with inspection and drafts. Add explicit approval gates for audience changes, tests, activation, scheduling, and sending.

Next Steps

• Follow the Grok Bot email marketing guide for practical workflows and prompts.
• Compare the 19 best email marketing tools for Grok Bot.
• Learn the underlying protocol in the complete MCP guide for email marketing.
• Read the complete Sequenzy MCP documentation.
• Build lifecycle strategy with the lifecycle marketing guide.

Official Sources

• Grok Bot overview
• Get started with Grok Bot
• Grok connectors and custom MCP
• Grok Bot approvals, security, and privacy
• Sequenzy MCP setup