Connect WarmySender to Grok Bot (Custom MCP Connector)
Grok supports custom MCP connectors and WarmySender speaks MCP, so you can add your workspace to Grok and run outreach in plain language. The server lives at https://warmysender.com/mcp and is already public (Grok's one requirement), so there is nothing to install or tunnel — you paste a URL and a key.
Who Can Use Grok Bot Today:
Grok Bot runs each of its agents on a cloud computer of its own, and ships as a desktop app for macOS and Windows (there is no Linux desktop app), plus iOS. On 26 August 2026 xAI widened access to SuperGrok and Cursor subscribers and reset weekly usage limits for everyone, so far more people can now put an agent to work. The qualifying tiers moved with that announcement, and xAI's own docs list them more narrowly than the announcement did — so check xAI's Grok Bot get-started page for the current list before you buy anything. (Grok Bot comes bundled with those paid subscriptions; it is not a free product.) Whichever way you reach Grok, the WarmySender connection below is the same.
Step 1 — Create Your API Key:
In WarmySender: Settings > API Keys > Create API Key. Name it "Grok", pick the scopes Grok should have (*:read only for monitoring; add the *:write scopes for full automation), and copy the key — shown once, starts with ws_.
Step 2 — Add the Custom Connector in Grok:
xAI documents this on the Grok web app: go to grok.com/connectors, click New Connector, select Custom, enter https://warmysender.com/mcp as the MCP server URL, and complete authentication with your ws_ key as the bearer token. On Grok Business and Enterprise, admins instead use the xAI console: + Add Connector > Other > same URL. Per xAI's docs, Grok then discovers the server's tools and makes them available in conversations. This is the route xAI documents for a custom MCP server, and connectors install account-wide rather than per-Bot — so once it is added here, Grok Bot sees it too.
Step 3 — Test:
Ask Grok: "Use the get_workspace_info tool to show me my WarmySender workspace." A reply with your workspace name, tier, and scopes means you're connected.
Using Grok Bot?
Grok Bot keeps its add-ons under Settings > Plugins — that is where installed connectors appear, and in a chat you type @ to attach one to the task. The Plugins page is also a catalogue you can browse, and WarmySender is not in that catalogue yet; our submission is in progress and we will update this guide the moment it appears. Two routes work today:
• Add the custom connector on grok.com exactly as in Step 2 above. It attaches to your Grok account, so your Grok Bot conversations can call the WarmySender tools.
• Running Grok Bot through Cursor? Add WarmySender to Cursor's own MCP configuration instead, using {"type": "http", "url": "https://warmysender.com/mcp"} with your ws_ key as the bearer token. That exact configuration is tested and working end to end. Per-client snippets for Cursor and every other tool: /documentation/mcp-install.
What Grok Can Do:
Run campaigns on cold email, LinkedIn, and Instagram (create/start/pause/resume/enroll, scheduler-paced within your safe caps and ramp), verify emails, search and export B2B leads, read mailbox health, tune warmup, and manage suppressions and tracking domains.
What Grok Can NEVER Do:
Send a message directly (launching only hands the campaign to the scheduler, which paces everything no matter who triggered it), raise a limit, connect or disconnect accounts, or delete anything permanently.
Troubleshooting:
Auth fails — the key must start with ws_ and not be revoked. "Insufficient scope" — add that scope to the key. Rate limited — wait a minute. Revoke any time by deleting the "Grok" key.
See also: "MCP Server — Connect AI Tools (Overview)" and "MCP Server — Safety, Scopes, and Rate Limits".