MCP server for Grok
MCP server for GrokCold email MCP server for Grok
Connect Grok to the Outreach2day MCP server as a custom connector on grok.com, from Grok Build, or through the xAI API. Grok quotes domains and mailboxes when you turn on Prepare orders at sign-in, runs warmup, launches campaigns and reads replies. You approve and pay every order on Stripe.
https://public.outreach2day.com/mcpCopies the server URL and opens Grok Connectors
Setup guide
- Choose New Connector → Custom
- Name it Outreach2day and paste the server URL
- Click Connect and sign in with your Outreach2day account
- Orders paid through Stripe after you approve them
- $2.50 per mailbox a month
Which of our mailboxes are ready to send, and which ones are dragging the inbox rate down?
- get_warmup_status40 mailboxes, inbox rate over 7 days
- get_campaign_statsQ4 campaign, per mailbox
Inbox rate, last 7 daysget_warmup_status
38 of 40 mailboxes are warm. Inbox rate 94% over 7 days.
Low: [email protected] (71%) and [email protected] (68%).
Both send in the Q4 campaign. Want the per-step stats before you decide?
- teams have used Outreach2day
- 3,600+
- emails sent a day
- 40M+
Among them
Can Grok run cold email through MCP?
Yes. On grok.com, add the server as a custom connector and sign in to Outreach2day. In Grok Build, add it with grok mcp add and sign in from /mcps. The xAI API takes it as a remote MCP tool with an API key in the authorization field. Grok then checks domains, quotes mailboxes (with Prepare orders turned on at sign-in), runs warmup, launches campaigns and reads replies while you pay each order on Stripe.
Cold email in Grok, step by step
- 01
Add the connector
Add the server URL as a custom connector on grok.com and sign in, or pass it to the xAI API as a remote MCP tool with your key in a header
- 02
Quote and pay
Grok asks for a quote and shows it to you. You approve it and pay on the Stripe page Grok links
- 03
Warm up and launch
Grok tracks setup and starts warmup. After 14 days of warmup and a passed preflight, ask Grok to launch
- 04
Watch the numbers
Ask Grok for replies and per-mailbox inbox rate. It flags weak mailboxes and pauses the campaign when you say so
Setup
Connect Grok
Add https://public.outreach2day.com/mcp to Grok and sign in with your Outreach2day account when it asks. Then ask: "Check my Outreach2day account status". An API key is only for CI and headless setups.
grok.com (custom connector)
OAuth sign-inConnectors, New Connector, Custom. Paste the server URL and sign in
- 1
Open grok.com/connectors, click New Connector, then Custom
grok.com/connectors
New Connector
Custom - 2
Name it Outreach2day, paste https://public.outreach2day.com/mcp as the Server URL and add it
Custom connector
Name
Outreach2dayServer URL
https://public.outreach2day.com/mcp - 3
Grok opens the sign-in in a pop-up window. If the browser blocks it, allow pop-ups for grok.com and click Connect again
grok.comAllow pop-ups
Outreach2day - 4
The first time the client connects, it opens an Outreach2day sign-in page in your browser. Sign in, turn on Prepare orders so the assistant can quote orders and create Stripe checkout links, and allow access
Sign in from Grok
Outreach2day - 5
On Grok Business or Enterprise, an admin adds the connector first in console.x.ai: Grok Business, Connectors, Add Connector, Other
console.x.ai
Grok BusinessConnectorsAdd Connector
Other
Grok Build CLI
OAuth sign-ingrok mcp add --transport http with the server URL, then sign in from /mcps
- 1
Add the server with the command below. It goes to ~/.grok/config.toml
Terminalgrok mcp add --transport http outreach2day https://public.outreach2day.com/mcp# then, in a grok session: /mcps, select outreach2day, press i to sign in - 2
Start grok, open /mcps, select outreach2day and press i. Grok Build also opens the sign-in on first use
/mcps
outreach2daypress i - 3
The first time the client connects, it opens an Outreach2day sign-in page in your browser. Sign in, turn on Prepare orders so the assistant can quote orders and create Stripe checkout links, and allow access
Sign in from Grok Build
Outreach2day - 4
For headless runs (grok -p, CI), add the server with a key header instead, shown under Setup details
xAI API
API key in a headerAn mcp tool in the request, with Bearer and your key in the authorization field
- 1
Create an API key in the Outreach2day app (API keys, New key) and export it as OUTREACH2DAY_API_KEY
API keys › New key
export OUTREACH2DAY_API_KEY=ot2d_••••••••
- 2
Add Outreach2day to tools as an mcp tool. xAI puts the authorization value into the Authorization header as written, so keep the Bearer prefix
curl · xAI Responses APIcurl https://api.x.ai/v1/responses \ -H "Authorization: Bearer $XAI_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "grok-4.7", "input": "Which of my mailboxes are ready to send?", "tools": [{ "type": "mcp", "server_label": "outreach2day", "server_description": "Cold email domains, mailboxes, warmup, campaigns and replies", "server_url": "https://public.outreach2day.com/mcp", "authorization": "Bearer '"$OUTREACH2DAY_API_KEY"'" }] }' - 3
Use allowed_tools to limit which tools Grok can call
Prompts
Things to ask Grok
Plain language is enough. The agent picks the tools and asks before anything costs money.
Setup details
Grok: files, sign-in and limits
What Grok's own documentation says about connecting a remote MCP server.
Works with Outreach2day
- grok.com custom connector with OAuth sign-in
- Grok Build CLI with OAuth sign-in, or a header from $OUTREACH2DAY_API_KEY for headless runs
- The xAI API with Bearer and your key in the authorization field
Does not work
- require_approval in the xAI API
- A local server with your key exposed through a tunnel for grok.com: use the hosted server
The same in every client
- tools, from domains to replies
- 24
- per mailbox a month
- $2.50
- of warmup and a green preflight before launch
- 14 days
- cold emails a mailbox a day from day 14
- 25
The tools Grok gets and the guardrails on orders are the same in every client: tool list, what the agent can and cannot do.
- Grok Build CLI
- Add the server by URL. Grok Build finds the Outreach2day sign-in on its own and keeps the token in ~/.grok/mcp_credentials.json. The entry goes to ~/.grok/config.toml, or .grok/config.toml with --scope project. xAI docs: Grok Build MCP serversGrok Build CLI
grok mcp add --transport http outreach2day https://public.outreach2day.com/mcp# then, in a grok session: /mcps, select outreach2day, press i to sign in - Grok Build, headless
- For grok -p and CI, send a key header. ${VAR} expands in the url and headers, so single quotes keep the key out of the file. grok mcp doctor checks the connection. xAI docs: Grok Build MCP serversGrok Build, headless
grok mcp add --transport http outreach2day https://public.outreach2day.com/mcp \ --header 'Authorization: Bearer ${OUTREACH2DAY_API_KEY}' - Servers you already have
- Grok Build also reads servers configured in ~/.claude.json, .cursor/mcp.json and .mcp.json. xAI docs: Grok Build MCP servers
- grok.com
- Connectors, New Connector, Custom, paste the server URL and sign in. Custom connectors are available to all Grok users; the server has to be reachable from the public internet. xAI docs: Grok connectors
- Grok Business and Enterprise
- An admin with Team Read-Write adds the connector first: console.x.ai, Grok Business, Connectors, Add Connector, Other. xAI docs: connector management
- xAI API
- An mcp tool with server_url, server_label, server_description, allowed_tools and authorization. xAI sends authorization as the whole Authorization header, so write it as Bearer and the key. require_approval is not supported, so the server's own guardrails apply: purchases stop at a Stripe link. xAI docs: remote MCP toolsxAI API
curl https://api.x.ai/v1/responses \ -H "Authorization: Bearer $XAI_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "grok-4.7", "input": "Which of my mailboxes are ready to send?", "tools": [{ "type": "mcp", "server_label": "outreach2day", "server_description": "Cold email domains, mailboxes, warmup, campaigns and replies", "server_url": "https://public.outreach2day.com/mcp", "authorization": "Bearer '"$OUTREACH2DAY_API_KEY"'" }] }'
What Grok can do with the server, job by job
Each page lists the tools for the job, an example session, prompts per assistant and the limits.
- Outbound end to endDomains, mailboxes, warmup, campaign and replies from one assistant
- Domains and mailboxesCheck names, quote, pay on Stripe and track setup; or connect your own domains
- WarmupStart warmup and get inbox rate, spam rate and ready date per mailbox
- CampaignsDraft the sequence, import contacts, launch, read stats and replies
- AI sales agentBuild an AI SDR on Claude, ChatGPT or Cursor: the toolkit, the build, cost and a comparison
Book a call
Book a 30-minute call
Talk to the team that runs the MCP server. We check your setup for Grok and your first order.
- Free 30-minute call
- Size domains and mailboxes for your volume
- Walk through a quote and the Stripe checkout
- Check your Grok setup
See open times in your time zone and book on this page.
Or open the booking pageLoading available times…
Open the booking page insteadCustomers
Teams that send with Outreach2day
“That was the best infrastructure and value for money I saw.”
“…deliverability with your inboxes is better than our outlook/google inboxes…”
“We really would like to thank you for that report. We don’t know what we are doing with email and it is very reassuring to us to know we have a partner on top of the ball.”
Questions
Or talk to the teamDoes Grok support MCP servers?
Yes. Grok supports MCP (Model Context Protocol) servers in three places: Grok Build (the CLI), custom connectors on grok.com, and the xAI API, which takes remote MCP servers as tools.
Can I connect the Outreach2day MCP server in the Grok app?
Yes. grok.com custom connectors take a remote MCP server URL; Grok opens the Outreach2day sign-in page and you allow access.
Can I limit which Outreach2day tools Grok can call?
In the xAI API, pass allowed_tools. Give a reporting agent only the read tools. The API has no approval step, so our server's own rules apply: no card is charged by a tool. On grok.com, open the connector and turn tools off one by one.
Does Grok Build pick up servers I set up for Claude Code or Cursor?
Yes. It reads ~/.claude.json, .cursor/mcp.json and .mcp.json, so a server you already added there shows up in Grok Build too.
Other AI clients
The same server and the same tools in every client. Only the setup differs.
Guides for MCP and the API
- Cold Email API for Domains, Warmup and RepliesWhat the Outreach2day cold email API covers: keys, workspaces, domain checks and purchase, mailbox lists, warmup, replies and export to Instantly or Smartlead.
- MCP for Cold Email Infrastructure: Domains and MailboxesGive an AI agent your cold email infrastructure through MCP: check domains, connect your own, list mailboxes. Which actions to allow, which to keep manual.
- Email Warmup API: Start, Pause and MonitorHow to run mailbox warmup through the Outreach2day email warmup API: enable, pause and disable operations, idempotency keys, polling and warmup states.
Run cold email from Grok
Domains, mailboxes, warmup, campaigns and replies from Grok. You approve every order.