GOOGLE ADS MCP SERVER

Your Google Ads data. A better conversation.

Bring campaign evidence into your AI assistant. Explore search intent, understand changes in spend and check conversion settings before deciding what to do next.

Connect your assistant

What you can do

Find the right account

Discover accessible customers and expand manager accounts. Read currency and timezone before comparing results.

Understand performance

Read campaign, keyword, search-term, landing-page and device reports over explicit date ranges.

Check the configuration

Inspect budgets, ads, conversion actions and recommendations. Use bounded GAQL queries for deeper analysis.

SETUP GUIDE

From connection to first answer.

You need an MCP client with remote HTTP and OAuth support, plus a Google login with access to the data you want to read. Client availability can depend on your plan or administrator.

Add a remote MCP server
Open your AI client’s MCP or connector settings. Add a server named “Adlane Google Ads” and paste the URL below. Choose Streamable HTTP if your client asks for a transport.
https://mcp.adlane.app/gads
Sign in and review consent
Start the connection in your client and follow the browser sign-in. Review the requested access, approve if appropriate, then return to your AI client.
Google uses its broad adwords permission for API access. Adlane exposes only read-only tools through this MCP. The shared Google consent screen may display Liftaven.
Check the tools
Refresh the connection if needed. You should see 13 tools, including list_accessible_customers. Ask your assistant to discover accounts before requesting a report.
Ask your first question
Start with a specific scope. Copy or adapt this prompt:
List my accessible Google Ads accounts. Ask me which customer to analyse, then check its currency, timezone and conversion actions. Compare the last 28 complete days with the previous 28 days. Explain changes in spend and conversions, cite the reports and flag missing data. Do not change anything.

Using a desktop client with local MCP configuration

If your client accepts an mcpServers JSON configuration but cannot connect to a remote OAuth server directly, the third-party mcp-remote bridge can make the connection. Install Node.js with npm first. Merge this entry into your existing configuration, restart the client and complete browser sign-in.

{
  "mcpServers": {
    "adlane-google-ads": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.adlane.app/gads"
      ]
    }
  }
}

The command downloads and runs mcp-remote on your computer. Native remote MCP support is preferable when your client provides it. Do not paste provider passwords or access tokens into the configuration.

Available tools

These tools read data. They cannot create campaigns, change budgets, publish ads or approve Adlane proposals.

list_accessible_customersget_customerlist_customer_clientslist_campaignslist_budgetslist_ad_groupslist_adslist_conversion_actionslist_recommendationslist_asset_groupsrun_reportsearchsearch_fields

Connection troubleshooting

No accounts or data?

Search-term reports omit privacy-filtered queries. Conversion value is not profit, and attributed conversions can change after the report date. Access also depends on Google Ads API approval and your account permissions.

Sign-in did not finish?

Complete consent in the same browser session. If a desktop bridge uses a local return address, allow that callback in your browser. Reconnect from the client if the sign-in expires.

Access stopped working?

Reconnect after access is revoked or a provider token expires. For Meta, expired tokens require a new sign-in. Check your provider permissions before repeatedly retrying a failed report.

Know what leaves your account.

Adlane keeps provider credentials server-side. Requested report data is returned to your chosen MCP client, which may share it with its AI provider. Review that client’s privacy settings before using sensitive reports.

Read Adlane’s privacy notice