AI Clients

Grok Bot

Grok Bot is xAI’s autonomous agent: it runs on a cloud computer, signs into your tools, and works on a schedule. It reaches remote MCP servers only, which is exactly what MCP Ads is. Add the server once and a Bot can read your ad accounts, draft changes, and hand you a report every Monday without being asked.

Add the server

Grok Bot’s custom-server form takes a name, a URL and optional headers. It cannot run the browser sign-in that Claude and Cursor use, so authenticate with an API key in a header instead.

  1. Create an API key

    In MCP Ads, open Manage → Connect MCP → API keys, name the key “Grok Bot” and create it. Copy it now: it is shown once.

  2. Open Settings → Plugins in the Grok Bot app

    Choose the option to add a custom MCP server rather than a marketplace plugin.

  3. Enter the server

    Name it mcp-ads, paste the URL, and add one header. Use the slim endpoint: Grok Bot discovers every tool on every connected server at once, and a large server can push that discovery past its timeout.

    Custom MCP server
    Name:    mcp-ads
    URL:     https://mcp-ads.com/mcp-slim
    Header:  Authorization: Bearer mcp_live_...
  4. Enable it for the Bot

    Plugins are per Bot. Open the Bot you want to use it with and switch mcp-ads on, then ask it to list your ad accounts to confirm the connection.

Careful

Grok Bot’s OAuth flow for custom (non-marketplace) MCP servers has been failing since its August 2026 beta — the desktop redirect is a plain-http localhost URL and the flow either rejects it or never starts. MCP Ads accepts that redirect, so the OAuth path will work the moment xAI fixes their side; until then the header is the reliable setup.

What a Bot can do with it

Everything the MCP tools expose: read performance across Google Ads, Meta, LinkedIn, TikTok, Snapchat, GA4 and Search Console, build campaigns, pause what is wasting money. Write tools still go through the confirmation and workspace policy controls, so a Bot proposes and you approve.

  • A Monday routine that pulls last week’s spend and results across every platform and drafts the summary
  • A daily check that flags any campaign spending with zero conversions and asks whether to pause it
  • A budget change described in plain language, turned into the exact platform edits, held for your approval
  • Cross-platform questions a single platform’s tools cannot answer — which channel produced the cheapest signups this month

Give the Bot a routine

A routine tells one Bot when to run a workflow. This is the one worth setting up first.

Routine: weekly ad report
When:  Every Monday at 08:00
Do:    Using mcp-ads, pull the last 7 days of spend, clicks, conversions and
       cost per conversion for every connected ad account. Flag any campaign
       with CTR under 0.5% or spend with zero conversions. Draft a summary
       with one recommendation per platform. Wait for my approval before
       sending or changing anything.
Tip

Use Test run on the routine before scheduling it. Bots follow their description literally; the phrase “wait for my approval” is what keeps write tools on the review path.

Go further

Common questions

Why an API key and not the sign-in?

Grok Bot’s form for a custom MCP server only carries a URL and headers, and its OAuth flow for servers outside the Cursor marketplace is currently broken on xAI’s side. The key is the same one the MCP Ads CLI uses: hashed at rest, revocable from the dashboard, and bound to the same plan limits as a sign-in.

Can I run MCP Ads locally and point Grok Bot at it?

No. Grok Bot works from a cloud computer and does not attach servers on your own machine; there is no localhost or stdio option. The hosted server at mcp-ads.com is what it needs.

Which Grok plans include Grok Bot?

During the beta, xAI lists SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra and Cursor Teams. Enterprise has a waitlist. Check x.ai/bot for the current list; it has changed more than once since August.

Which endpoint should I use?

https://mcp-ads.com/mcp-slim. It exposes one tool per platform that takes an action name, so discovery is fast. The full /mcp endpoint lists every tool individually, which is more than Grok Bot needs to load and slower to discover.

What happens if I revoke the key?

The Bot’s next call is refused with a 401 and it stops. Create a new key and update the header in Settings → Plugins to resume. Revoke first if a machine that held the key is gone.

Ready to connect?

Start free, connect the platforms you use, and run your first workflow from Claude in minutes.