One platform, two ways to work
Use a compatible assistant or the browser workspace. Campaign drafts, reports, and reviewed changes use the same saved records and service workflows.
Product / MCP
Advarde connects a compatible ChatGPT, Claude or Codex client to your existing OpenAI Ads accounts through MCP. Ask for account data, prepare campaigns and review the same saved work in your browser.
Compare this week’s campaigns and prepare two new variations from our brief.
I can compare the results, draft the variations, and save them for your review.
ads_list_accountsads_get_performance_reportads_save_campaign_draftYour workspace permissions apply.
Use a compatible assistant or the browser workspace. Campaign drafts, reports, and reviewed changes use the same saved records and service workflows.
Connect with OAuth or a revocable bearer token where your client supports it. Advertiser credentials remain in Advarde, separate from your conversation.
Ask about results, prepare campaign drafts, and review proposed changes. Writes follow your permissions and the exact action or policy you authorize.
How it works
Use Advarde in the browser or through a connected assistant. The account, workspace, and review stay attached to the work.
Add the API credentials for an existing OpenAI Ads account in your workspace.
Use the MCP endpoint and authentication instructions in MCP connections. Choose the workspace the assistant may access.
Start with account reads, then use the same campaign and reporting workflows as your team.
Connect your workspace, confirm the selected account and complete your first useful request.
Start with a clear account and result. Read access, saved workspace work and live advertising changes have different requirements.
List connected accounts and read insights for a stated period. Confirm currency, timezone and missing fields before interpreting the result.
“Show spend and clicks for the account I select. Use 1–7 September 2026 and state its timezone. Do not change anything.”
Keep a report or supplied brief in the shared workspace. Saving requires workspace write access. A draft stays local until a reviewed build is applied.
Follow the review workflowRetrieve installation instructions and inspect recent browser receipts. A configured event, an observed call and an attributed conversion are separate observations.
Diagnose missing conversionsCopy the complete HTTPS endpoint ending in /mcp from MCP connections. Prefer OAuth when supported; other compatible clients can use a revocable workspace token in their credential settings. Keep advertiser credentials in Advarde.
If account reads work but a saved report or draft is denied, check the workspace role, tool scope, account write setting and subscription requirements. A prompt cannot grant missing permissions.
Read the developer guideA few useful answers
Use clients that support compatible remote MCP connections, including ChatGPT, Codex, Claude, Hermes, and OpenClaw where supported and enabled. Availability and authentication options depend on your client and workspace settings.
No. Store advertiser credentials in Advarde. Connect the assistant using workspace-scoped OAuth or a bearer token configured through the client’s credential settings.
Yes. Revoke tokens or OAuth access in your workspace. Team roles and access are checked when tools run. Removing assistant access does not itself pause live advertising.
No. You need an eligible advertiser account and its Advertiser API credential. Advarde is independent software; your assistant subscription, Advarde subscription and advertising spend are separate.
Yes. Start with read access to inspect accounts and insights. Saving a report or draft is a workspace write and requires the corresponding permissions, even though it does not change live advertising. Creating or launching ads has its own reviewed workflow.
Connect your existing advertiser account and keep the work together.