How to run sales prospecting and outbound from Grok Bot

What Grok Bot is, and where GTM work fits

Grok Bot gives you Bots that persist: each has a name, a job and context that builds up over time, and works on a persistent cloud computer with a browser, a filesystem and a terminal, so work continues while your laptop is closed. It is included with every paid individual Cursor plan and the Cursor Teams plan, you can link a SuperGrok subscription, and under The X Subscription it comes with the Premium, Super and Ultra plans.

Its own use-case page starts with a Sales Outbound Bot: research the accounts in a CRM view, score them against your ICP and recent intent, find up to three contacts per account, draft email and LinkedIn outreach, skip anyone already in an active sequence, and return a review list without sending or enrolling anyone. Then, once the output is reliable, a nightly routine that stops at the review list.

That prompt assumes the Bot can reach a CRM, a lead source, an email finder and a sequencer. OXYGEN is that workspace in one connector, so the review list, the enrichment, the sequence and the CRM record are the same data instead of four tools the Bot clicks through.

Sources: Grok Bot overview (docs.x.ai), Grok Bot on The X Subscription, Grok Bot: Use cases (Sales Outbound)

How Grok Bot connects to a custom MCP server

Grok Bot calls connectors plugins. You install them from Connect apps in the sidebar, authenticate in your browser when asked, and type @ in chat to attach one to a task. Installed connectors are account-wide, so every Bot on your account can use them.

The Team Bots page lists two kinds of custom MCP server a Bot can carry. A Remote HTTPS server uses the Bot's own credential, or each person's own sign-in when the server uses OAuth. A Command server runs on the computer the conversation uses, and the docs say to choose Remote HTTPS for a custom server that needs secrets. OXYGEN's server is remote and uses OAuth, so it is the Remote HTTPS kind, and on a Team Bot each teammate signs in once and works as themselves.

On a Cursor team, Grok Bot follows the team's connector policy. Admins set which servers members can use from the Team Marketplace on the dashboard's Plugins & MCPs page, Enterprise teams can also keep an MCP allowlist, and a blocked server shows as Disabled by team admin. Grok Bot's docs show where a Team Bot's plugins live (its Setup section, or by asking the Bot in chat) but print no separate click path for adding a custom server to a personal Bot, so the steps below ask the Bot in chat.

Sources: Grok Bot: Use the computer and apps, Grok Bot: Team Bots (plugins and custom MCP servers), Grok Bot: Teams and enterprises (connector policy), Cursor help: Connect apps in Grok Bot

What OXYGEN gives your Bot to work with

OXYGEN is one GTM workspace an assistant operates through its hosted MCP server. It holds a CRM (companies, people, deals and objects you define, a deals pipeline and an activity timeline), tables you edit like a spreadsheet with enrichment and AI columns, email waterfalls across 17 providers and phone waterfalls across 13, charged only when one finds the value, sequences that mix email, LinkedIn and WhatsApp steps, and one inbox for the replies.

Because those parts share one record per lead, the joins are already made. A reply on LinkedIn stops the email steps for that lead, the replier is filed as a person on the CRM, and a lead you enriched last month is not paid for twice. Every run the Bot starts shows up in the web app with its cost, results and a link, so a teammate who never opens Grok Bot can see what happened.

• Account research: hiring, funding, news and tech stack for a target account, written onto the company record.
• Building lists: people and company searches by title, industry, headcount and location, saved into a table.
• Enriching lists: work emails and phone numbers through waterfalls, plus AI columns that score fit or write a first line.
• Writing sequences: email, LinkedIn and WhatsApp steps in one sequence, with branches and up to 26 versions of a step.
• Updating the CRM: records, notes and tasks, with replies landing on each person's timeline.
• Reading replies: one inbox across email, LinkedIn and WhatsApp, with AI triage and drafted answers to review.

Approvals before sends and paid steps, on both sides

On the OXYGEN side, previews and dry runs make no provider calls and spend nothing. A paid provider call, an AI or enrichment column run, a live workflow call, CRM sync, LinkedIn engagement or pushing leads into an external campaign refuses to run until it carries an approval, and anything with a price also needs a credit ceiling. Starting a sequence needs approval too, plus a cap on live sends when it has email, WhatsApp or CRM-task steps. Enrolling leads is free, and an active sequence contacts new leads on its next tick under its launch approval, so enroll into a draft until you are ready.

On the Grok Bot side, an action that needs approval shows its operation and inputs with Allow once, Always allow or Deny. Grok Bot's FAQ suggests narrow Ask first rules for sending, publishing, deleting, purchasing or changing production systems, and you write them under Settings, Bot, Auto-review, Custom Rules. An approval raised by work that started without you, such as a routine, expires after about ten minutes and the action does not run.

Use both. OXYGEN's gate is a parameter the Bot sets after you agree, so an Ask first rule for OXYGEN's live steps puts the card in front of you before the Bot sets it.

Sources: Grok Bot: Approvals, security, and privacy, Grok Bot FAQ, Cursor help: Grok Bot how-tos (Auto-review)

Routines: what to schedule, and where to stop

A Grok Bot routine tells one Bot when to run a workflow, on a schedule with a time zone or after a supported event, and posts the result in that Bot's conversation. Grok Bot's guidance is to make a one-time task reliable, save it as a skill with its approval rules, and only then automate it.

For GTM that maps to read-and-prepare work: a weekday routine that checks new replies in OXYGEN's inbox, lists accounts that showed a signal, or refreshes a table of new hires at target accounts, then stops at a review list in chat. Keep launches, sends and paid enrichment as attended steps, since an unattended approval expires before you see it.

Sources: Grok Bot: Skills and routines, Grok Bot: Use cases (Sales Outbound)

Grok Bot, Grok chat and Grok Build add MCP servers differently

Searches for grok mcp mix three products. Grok chat on grok.com adds a custom MCP connector from grok.com/connectors: New Connector, then Custom, then the server URL and any sign-in; the server must be reachable over the public internet, and on Grok Business and Enterprise a team admin provisions connectors first. Grok Build, the terminal tool, adds remote servers with grok mcp add --transport http followed by a name and a URL, and handles OAuth in the browser on first use.

Grok Bot is the third: custom servers are plugins, as described above. OXYGEN's endpoint is the same URL in all three, https://oxygen-agent.com/mcp. This page covers Grok Bot because it is the one built for standing jobs like outbound.

Sources: Grok connectors, custom MCP (docs.x.ai), Grok Build: MCP servers (docs.x.ai)

What to know before you start

• We have not yet run OXYGEN's server inside Grok Bot ourselves; it is set up as any other MCP client, so menus may differ from the steps above.
• OXYGEN's inline table widgets render only on MCP-Apps hosts; in Grok Bot, open the web_url in each result to see the grid.
• OXYGEN's approval is a parameter the Bot sets after you agree, so keep Grok Bot's Ask first rules on for live steps.
• Large CSV files do not go through chat; OXYGEN returns an import command to run where its CLI is installed.
• OXYGEN has no contact database of its own: leads come from data providers on credits, and sending needs a paid plan.
• LinkedIn automation carries risk to the connected account; keep daily volumes modest.