How to Connect Google Ads and Meta Ads to Claude or ChatGPT with an MCP Server

#mcp #googleads #ai #marketing

If you want an AI assistant to read your Google Ads and Meta Ads performance and prepare changes in plain language, you need a connection that is both standard and scoped. The Model Context Protocol (MCP) is that standard. This tutorial shows how to connect the Ovaideu MCP server to Claude or ChatGPT for Google Ads and Meta Ads work.

Ovaideu is AI ad operations software for Google Ads and Meta Ads. Its API & MCP page lists the workflows the connector supports, including building and optimizing Google Ads campaigns and working with Meta Ads campaigns, ad sets and reporting. The steps below follow that page.

What you need

An Ovaideu account. Ovaideu offers a free trial with no card required, and paid plans start at $47 per month. Current plan details are on the pricing page.
Access to the Google Ads and/or Meta Ads accounts you want to manage. Ovaideu only works inside the account access you authorize, as described on the security page.

Step 1: Connect your ad accounts

Connect the ad accounts you want the assistant to work with. Platform overviews are here: Google Ads, automated and optimized and Meta Ads, automated and optimized.

Step 2: Create your own MCP key

Sign in to Ovaideu, activate MCP access, and create a user-bound key from the MCP keys section of the dashboard. Keep the key private. Do not paste it into posts, screenshots or shared notebooks.

Step 3: Add the connector

The MCP server endpoint is https://ovaideu.com/api/mcp. The same server is also reachable at https://ovaideu.com/mcp. Requests use a bearer header:

Authorization: Bearer YOUR_OVAIDEU_API_KEY

For Claude on a Pro, Max, Team or Enterprise plan, open Settings, then Connectors, choose Add custom connector and paste the endpoint. For ChatGPT, open Settings, then Connectors, choose Add custom connector and paste the endpoint. Authenticate with your key and complete the Google or Meta sign-in in your own browser.

If you call the API directly from your own code, add the Authorization header yourself. Example notes and reference files are in the public ovaideu-mcp-examples repository on Codeberg.

Step 4: Start with read-only prompts

Begin with questions that cannot change anything. Good first prompts include:

"Summarize spend, clicks and conversions for my Google Ads account over the last 7 days."
"Which Meta Ads ad sets spent the most last week without a conversion?"
"List the search terms that used budget this month and suggest negative keywords for my review."

Review every proposed change before it goes live. Increase permissions only after the answers match what you see in the dashboard.

Step 5: Check the tracking behind the answers

An assistant is only as useful as the data behind it. Ovaideu also covers Google Analytics 4, Google Tag Manager, Google Search Console and Google Business Profile, so you can check conversion tracking in one place before you let any tool change budgets:

For the full list of connected tools, see the integrations page and the platforms overview.

Who runs Ovaideu

Ovaideu is operated by OIESU (OPC) Private Limited, a registered company in West Bengal, India. You can read more on the about page or send a message through the contact page. For setup help and account questions, see support or email support@ovaideu.com.

Thanks for reading. If you build something with the Google Ads or Meta Ads MCP connector, write to support@ovaideu.com.

DEV Community