Grok’s chat app and its CLI, Grok Build, both speak remote MCP with OAuth, so MCP Ads connects the same way it connects to Claude. Grok Bot, the autonomous agent, is a separate client with its own page.
Add the server
Pick the surface you use. All three take the same URL.
On grok.com open Connectors from the + button, choose New Connector, then Custom. Paste the URL and finish the sign-in when it opens. On mobile it is under Settings → Connectors.
Custom connector
https://mcp-ads.com/mcp-slim
Authorise
The chat app and Grok Build open a browser window for the MCP Ads sign-in on the first call. Approve it once; the grant persists and refreshes on its own.
Where this helps
Asking about spend and results across every platform in one chat, without opening a dashboard
Building a campaign in conversation and reviewing the exact changes before they go live
Grok Build: pulling live ad metrics into a script or a report from the terminal
Does the Grok chat app need a paid plan for custom connectors?
xAI’s documentation covers Grok Business and Enterprise; consumer reports put custom connectors behind SuperGrok or X Premium+. Confirm on x.ai before assuming a free account can add one.
Is there a one-click install like Claude’s?
Not for Grok. There is no query-parameter deep link into the connector form, so the URL is pasted. Grok Build’s single command is the closest equivalent.
Why does the API example use a key instead of OAuth?
The xAI API’s mcp tool only carries an authorization value and headers; there is no place for an authorization-code flow to run. An MCP Ads API key fills that field. Create one under Manage → Connect MCP.
Ready to connect?
Start free, connect the platforms you use, and run your first workflow from Claude in minutes.
Grok & Grok Build
Claude