Skip to content

Grok OpenAI Ads MCP get_ad_group

How to: Grok OpenAI Ads MCP get_ad_group

client:Grok transport:streamable-http tool:get_ad_group

Add OpenAI Ads MCP to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "openai-ads-mcp": {
      "type": "http",
      "url": "https://openai-ads-mcp.trakkr.ai/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something get_ad_group does. Grok lists the server's tools on connect and calls get_ad_group itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that OpenAI Ads MCP's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Set these first

OpenAI Ads MCP will not start until these are set, so get_ad_group never becomes available.

  • OPENAI_ADS_API_KEY
  • OPENAI_ADS_MCP_READONLY
  • OPENAI_ADS_BUDGET_CEILING_USD

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.