On this page6
Connect Claude to ChatGPT Ads through Otto's hosted HTTP MCP server (connect Claude to Otto MCP) using a single organization-scoped token prefixed otto_mcp__ to audit campaigns, ad groups, and conversion metrics alongside GA4 and Google Search Console without pasting OpenAI Advertiser API keys into your AI client. Across Otto MCP's 227 tools across 15 integrations, querying aggregated metrics cuts Claude token usage by 80–90% compared to uploading 3,000-row CSV exports, while human approval gates keep new ads paused and website landing-page updates in WordPress drafts or GitHub pull requests.
Copy-paste Claude prompts to test your ChatGPT Ads + Otto MCP connection
You can test your connected ChatGPT Ads account immediately using these five prompts. If you manage multiple ad channels, review 10 Claude workflows for Meta Ads in 2027 for complementary creative workflows.
Prompt 1: ChatGPT Ads performance audit across all reporting levels
Run an audit on my ChatGPT Ads account for the last 14 days using the Insights tools.
Break down performance by account, campaign, and ad group.
For each entity, pull:
1. Impressions
2. Clicks and CTR
3. Spend
4. Conversions and Cost per Conversion
Flag any ad group with spend above $150 that has zero conversions, and list the top three ads ranked by CTR.
Prompt 2: Cross-channel CPA reconciliation against GA4
Compare paid campaign performance over the last 30 days across ChatGPT Ads, Meta Ads, and LinkedIn Ads.
Query GA4 runReport to pull sessions, conversions, and revenue filtered by:
utm_source=openai&utm_medium=paid
utm_source=meta&utm_medium=paid
utm_source=linkedin&utm_medium=paid
Reconcile reported platform conversions against GA4 recorded events.
Display a summary table with Platform, Ad Spend, Platform Conversions, GA4 Conversions, Platform CPA, and GA4 CPA.
Use Otto Website Analytics and GA4 reporting to verify conversion tracking setup before scaling spend.
Prompt 3: Stage a paused ChatGPT Ads campaign with explicit bidding and UTMs
Stage a new ChatGPT Ads campaign with the following parameters:
- Name: "Spring 2027 - Pilates Intro Offer"
- Status: "paused"
- Objective: conversions
- bidding_type: "conversions"
- Daily budget: $35.00
- Query template: utm_source=openai&utm_medium=paid&utm_campaign={campaign_id}&utm_content={ad_id}
Do not activate the campaign. Show me the staged payload and confirm that status is set to paused.
Prompt 4: Audit destination landing page speed and OAI-AdsBot readiness
Run psi_analyze_url on my destination landing page URL: https://yourdomain.com/your-offer-page
Check mobile Core Web Vitals, Largest Contentful Paint (LCP), and Cumulative Layout Shift (CLS).
Then inspect the page content:
1. Is the headline and offer consistent with our ad copy?
2. Are pricing and booking steps clearly visible above the fold?
3. Is our robots.txt allowing OAI-AdsBot?
List three specific fixes to improve post-click conversion rates.
Prompt 5: Stage a conversational landing page update in WordPress draft
Based on the top-performing search intents from our ChatGPT Ads audit, draft an updated hero section and FAQ block for our landing page.
Prepare this as a WordPress draft update on page ID 42 using the WordPress toolset.
Do not publish the page live. Leave the status as draft and provide the preview URL so I can inspect it.Manual CSV exports vs. DIY OpenAI Advertiser API scripts vs. Claude + Otto MCP
Three common approaches are manual CSV uploads, DIY calls to api.ads.openai.com, and a hosted MCP gateway. The table below contrasts token use, cross-channel reporting, and where API keys live.
| Operational capability | Manual Ads Manager CSV exports | DIY scripts to api.ads.openai.com | Claude + Otto MCP (otto.islaintel.com) |
|---|---|---|---|
| Authentication & credentials | Web session login; manual file downloads | Raw API keys stored in local .env files or curl headers | Remote HTTP MCP with one otto_mcp__ token; keys stay on server |
| Token consumption per turn | 40,000 to 80,000 tokens per 3,000-row CSV file | Variable; requires custom aggregation logic | 80–90% reduction via filtered, aggregated MCP tool calls |
| Cross-channel reconciliation | Manual spreadsheet stitching across platforms | Separate scripts required for each advertising API | Unified queries across ChatGPT Ads, Meta, LinkedIn, and GA4 |
| Safety and spend control | Changes must be applied by hand in each UI | Unrestricted write access if script holds write tokens | Human approval gates; new ads stay paused by default |
| Landing page integration | Disconnected from CMS and hosting platforms | No connection to CMS, DNS, or deployment pipelines | Stages WordPress drafts or GitHub pull requests with Vercel previews |
| Supported AI clients | Web chat uploads only | Custom per-client development | Claude Desktop, Claude Web, Cursor, and Claude Code |
Connect Claude to Otto MCP to audit ChatGPT Ads, GA4, and landing-page tools from Claude without pasting Advertiser API keys into your AI client.
Otto MCP
Ask your AI assistant what changed in your ads
Connect Claude or ChatGPT to Otto, then ask about Meta Ads, Google Ads, GA4, and Search Console in the same chat. The logins stay in Otto.
How to connect Claude to ChatGPT Ads in 5 steps via Otto MCP
Setting up Claude with ChatGPT Ads takes five steps. According to the Model Context Protocol remote server specification, remote MCP servers connect over HTTP without requiring local code installations on each client device.
Step 1: Authorize ChatGPT Ads inside your Otto organization
Connect ChatGPT Ads, GA4, and your CMS inside your Otto organization. The OpenAI Advertiser API Reporting documentation instructs keeping Advertiser API keys on the server; Otto stores OAuth credentials there and your AI client never holds raw OpenAI keys. Follow the Connect ChatGPT Ads to Otto setup guide.
Step 2: Copy your hosted Otto MCP endpoint and bearer token
Navigate to the MCP tab in Otto Settings to locate your server URL and API key:
- Server URL:
https://otto.islaintel.com/api/mcp - Bearer token:
otto_mcp__your_unique_key
Step 3: Add the remote MCP connector in Claude
In Claude Desktop or Claude Web, open Settings → Connectors (Custom Connectors) and add a remote MCP server. Remote MCP servers run over HTTP with server-side authentication—no local install per device. Enter https://otto.islaintel.com/api/mcp and paste your otto_mcp__ bearer token into the Authorization header. Cursor and Claude Code use the same URL and token; see How to Connect Claude to Otto MCP for client-specific screens.
Step 4: Run your first read-only ChatGPT Ads Insights audit
Ask Claude to pull account-, campaign-, ad-group-, or ad-level delivery metrics through the four OpenAI Advertiser API Insights endpoints (GET /v1/ad_account/insights, /v1/campaigns/{campaign_id}/insights, /v1/ad_groups/{ad_group_id}/insights, and /v1/ads/{ad_id}/insights). Example prompt: List my active ChatGPT Ads campaigns and last week's spend and impression totals. Otto MCP returns aggregated rows without a CSV upload.
Step 5: Stage paused campaigns and approve changes
When drafting new campaigns, Otto requires explicit safety parameters. According to the OpenAI Advertiser API Campaign Management documentation, campaigns support status: "paused" and require an explicit bidding_type of impressions, clicks, or conversions at https://api.ads.openai.com/v1/campaigns.
Include a standard tracking template on all staged campaigns: utm_source=openai&utm_medium=paid&utm_campaign={campaign_id}&utm_content={ad_id}
On Pro, staged ads remain paused until an account Reviewer or Admin approves them in the Otto web dashboard or via WhatsApp. Learn more about automated guardrails in the Otto AI Paid Ads Manager.
How ChatGPT Ads and OAI-AdsBot work—and what your landing page must include
OpenAI's Advertiser API uses Ad account → Campaign → Ad group → Ad, as detailed in the OpenAI Advertiser API Campaign Management documentation. See what OpenAI announced for ChatGPT Ads for product background.
How OAI-AdsBot differs from OAI-SearchBot
The OpenAI crawler documentation lists two agents operators care about: OAI-AdsBot visits submitted ad landing pages for policy checks and relevance signals (without using that data to train foundation models), while OAI-SearchBot indexes pages for organic ChatGPT Search separately.
When you submit a destination URL, OpenAI may visit the landing page to ensure it complies with policies and may use content from the page to determine when the ad is most relevant to show. If robots.txt blocks OAI-AdsBot, that fetch may not run—so policy and relevance checks that depend on the crawl can fail. Otto never guarantees search engine rankings or ChatGPT citations. Otto structures landing pages, schema markup, and metadata so search engines and AI assistants can read your business clearly.
Destination landing page requirements
Because OAI-AdsBot parses landing pages to assess ad relevance, destination pages must directly match the conversational context of user queries. An effective ChatGPT Ads landing page should provide:
- Clear proposition above the fold: State the exact service, target customer, and location immediately.
- Transparent pricing and service tiers: Put session length, price, or tier names where a reader can see them without opening another page.
- Fast mobile load performance: Mobile speed matters for post-click experience on conversational ad traffic. Otto MCP includes
psi_analyze_urlto run Lighthouse and Core Web Vitals audits using Otto's platform key. On June 15, 2026 (v1.1.5), Otto deployed automated image compression to keep mobile assets optimized.
Say you run a sports therapy clinic with a "Post-Marathon Recovery" ChatGPT Ad: the landing page should name the service and city above the fold, show session length and price before the booking widget, and list licenses and privacy links in the footer.
Updating destination pages via WordPress drafts and GitHub pull requests
Unlike ad-only management platforms, Otto updates the landing page alongside the ad campaign. Otto is not a website builder; he works directly on your existing site.
WordPress sites get 29 MCP tools (15 read, 14 write); new posts and pages default to draft. Custom codebases can stage GitHub pull requests with Vercel preview URLs.
Enrique Gomez, owner of Enzo Maverick Pilates and Experiences Sensory, notes: "Otto has been pivotal for us. The ease of making website changes on the fly lets us sharpen our brand and revise as fluidly as we need.". Explore landing-page workflows in the Otto AI Website Manager.
Permission gates and safety: how Otto prevents unapproved ad spend
Claude holds only an otto_mcp__ token; Otto stores integration OAuth keys and routes read calls versus approval-gated writes by plan and role.
Read-only integrations across all plans
GA4 (runReport), Google Search Console, YouTube, Google Sheets, and PageSpeed Insights stay read-only on every plan. Ad changes need Pro, and Google Business Profile allows local posts on every plan.
Staged write permissions and approval requirements
When managing paid campaigns and content on the Pro plan, write actions require explicit verification:
- ChatGPT Ads: New campaigns stage with
status: "paused"and require owner sign-off to activate. - LinkedIn Ads: Campaigns and ad sets default to
DRAFTstatus. Pausing or unpausing requires an explicitconfirm=trueparameter alongside Reviewer or Admin rights. The MCP connector rejects$0budgets automatically. - Meta Ads: Write operations require Reviewer or Admin permissions. If you also manage Meta campaigns, see our guide on how to connect Claude to Meta Ads in 2027.
- WordPress: Content modifications default to draft. Checkout, contact, and legal pages always require explicit human approval in Otto core.
- Social media publishing: Publishing to Facebook Pages and Instagram via Otto MCP goes live immediately and requires Reviewer or Admin access.
- Reviewer workflows: Approvals can be granted through the web interface or directly within WhatsApp without opening the dashboard. The tool
otto_get_change_logtracks recent deployment records.
Otto Webmaster vs. Opteo, Madgicx, Synter, and Ryze AI: plans, limitations, and FAQs
Single-channel optimizers, connector marketplaces, and full webmaster stacks solve different problems. See 7 best Ryze AI alternatives for paid ads and SEO in 2027 for a wider market view.
| Feature / capability | Opteo | Madgicx | Synter | Ryze AI | Otto Webmaster |
|---|---|---|---|---|---|
| Supported channels | Google Ads only | Meta Ads focus | 40+ ad networks | Paid ads & SEO/GEO | Paid ads (Meta, Google, LinkedIn, X, ChatGPT Ads), SEO, Socials |
| Claude MCP connection | No Claude MCP connector | Meta creative analytics; rule-based bid automation | Ad connector for Claude, ChatGPT, Cursor | Claude-focused paid ads/SEO workflows | Hosted HTTP MCP server with 227 tools across 15 integrations |
| Landing page updates | None | Meta Ads focus (creative analytics, bid automation) | No website or technical SEO deploys | No live GitHub PRs or WordPress draft deploys | WordPress drafts (29 tools) and GitHub PRs with Vercel previews |
| Safety model | In-app recommendations | Rule-based automation | Paid media connectors; no website or technical SEO deploys | Paid ads & SEO/GEO focus; no live GitHub PR or WordPress draft management | Ads stay paused; read-only ad protections; owner sign-off |
Otto pricing and plans
Otto MCP comes with every plan, and Starter is MCP only. Details are on the Otto Starter, Pro, and Enterprise plans page:
- Starter: $9.99/week or $29.99/month, paid in full. MCP only: reads every connected source in Claude, ChatGPT or Cursor and publishes posts to Instagram, Facebook Pages, LinkedIn and Google Business Profile. No scheduling, ad changes, image generation or site edits.
- Pro: $199/mo, or $99/mo billed annually ($1,188/year), starting with $1 for 3 days. Adds the Otto app, website updates and SEO, ad changes, post scheduling, comment replies, image generation and team seats, with a homepage redesign included with the $1 trial. Otto also sends automated weekly SEO reports.
- Enterprise: no published price; a call with the founder, for bigger businesses and agencies. Cancel anytime.
Honest limitations
Ad changes require Pro (Starter reads ads and publishes social posts); agency white-labeling on client portals is limited; the Otto CLI is coming soon while HTTP MCP is supported today; and Wix, Webflow, and TikTok are not live integrations.
Frequently asked questions
Can Claude spend my ChatGPT Ads budget automatically?
No. New campaigns created through Otto MCP stage with status: "paused". On Pro, campaigns cannot activate or spend budget until an account Reviewer or Admin approves the change in the web app or via WhatsApp.
How does Otto protect my OpenAI Advertiser API keys?
You never paste raw OpenAI keys or GA4 secrets into Claude prompts or desktop configuration files. Credentials stay isolated on Otto's server, and your AI assistant interacts solely through an organization-scoped bearer token prefixed otto_mcp__.
Why query ChatGPT Ads via MCP instead of uploading CSV exports?
Uploading a raw 3,000-row ad export can consume 40,000 to 80,000 tokens in a single turn. Otto MCP tools retrieve pre-aggregated metrics directly from the OpenAI Insights API, reducing context token consumption by 80–90% while allowing direct reconciliation against live GA4 data.
What happens to my landing page when ad performance drops?
Unlike ad-only tools, Otto can draft landing-page fixes immediately. Claude can audit Core Web Vitals using psi_analyze_url, identify copy mismatches, and prepare an updated hero section as a WordPress draft or GitHub pull request in the same session.
Connect Claude to Otto MCP to connect your ChatGPT Ads account, audit campaigns, and optimize destination pages within a secure operating environment.
Otto AI Paid Ads Manager
The ad should match the page.
Otto watches the accounts next to the live site. Creative and budget stay drafts until you approve them. The weekly note says what the spend did.
See how Otto does it