AdAce AdsConnect ChatGPT to AdAce Ads through MCP and verify the first read
ChatGPT can request AdAce Ads tools through an authenticated MCP connection. The useful outcome is a traceable read for the intended workspace and client, followed by an answer you can check. The implemented server and local tests are preparation for this workflow; they do not certify live ChatGPT OAuth acceptance or a public directory listing.
Advertising access and AI access are separate
There are two independent connections. AdAce Ads must have access to advertising data, and ChatGPT must be authorized to call AdAce Ads. Connecting ChatGPT does not grant Google or Meta permissions or import campaigns. Complete the relevant provider connection and inspect its data first. Otherwise a correctly authenticated AI client may receive an empty campaign list or a data-unavailable response, which should not be presented as a business conclusion.
The AdAce Ads Connect AI page provides the deployment's MCP address and connection guidance. Its OAuth consent chooses a workspace and access scope. Subsequent calls remain subject to the user's current role and client assignments. Start with read access for reporting. A propose scope is different: it can create change proposals, and a configured auto policy may allow eligible proposals to progress without separate human approval. Do not add this scope simply to fix a read problem.
A practical first question is: 'Call get_started in AdAce Ads, then list the clients I can access. Read North Store's campaigns for the selected account; identify the account and the source of each number. If data is unavailable, explain the missing step.' Use the returned client and account identifiers rather than guessing from names. For a performance comparison, specify exact dates and ask which days remain preliminary before discussing causes or recommendations.
Selected tools can return structured results and optional chat cards. A card helps inspect a summary, but its appearance is not evidence of fresh provider data or a completed change. Check the tool result, reporting period and data state. Keep the initial verification to reading; write-capable tasks require separate permissions and operational readiness. Model-generated text, tool results and application approvals are different forms of evidence.
A report you can reproduce
- Review advertising in a conversation while retaining the workspace, client and account context behind the answer.
- Ask for specific tool results and dates so another teammate can reproduce a comparison without trusting an unsupported summary.
- Diagnose authentication, client access and missing advertising data independently instead of broadening permissions unnecessarily.
Authorize and verify one read
- Open Connect AI in AdAce Ads and copy the MCP address for the approved deployment. Use the advertised endpoint; do not invent a production URL or enter a provider token.
- Follow the current ChatGPT custom MCP connection instructions. OpenAI's documentation currently uses Developer mode under Settings → Security and login, then ChatGPT Plugins to add the connection. Availability depends on the account and workspace policy.
- For AdAce Ads' documented public-endpoint route, enter its HTTPS address including /mcp. Complete AdAce Ads authorization and choose the intended workspace with read access where offered.
- Start a new conversation with the connection enabled and request get_started. Ask an owner or administrator to refresh the activity panel in the same AdAce Ads workspace.
- Run one client and campaign read, compare a recognizable record with the application, and only then request a dated performance explanation. Record errors without copying authorization codes or tokens.
Connection, metadata and data problems
- No custom connection option: check ChatGPT's current account eligibility and workspace administrator policy. This article does not promise access on a particular subscription or device.
- Authorization fails: verify the MCP endpoint and the workspace chosen on consent. A browser session that opens AdAce Ads does not prove ChatGPT can reach the server. Deployment, discovery or callback failures need the operator rather than a fabricated URL.
- Connected but no tools or stale schemas: review the connection metadata, refresh it where supported and start a new conversation. If calls work but records are missing, check role, client assignments, imported campaigns and collection status. Revoke unneeded AI grants on Connect AI; successful revocation does not erase data already returned to a conversation.
Sources and further reading
Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace