MCP
Claude Desktop MCP Google Ads Configuration Guide — Complete 2026 Setup Tutorial
Configure Claude Desktop MCP Google Ads integration in under 15 minutes with this complete configuration guide. Connect live Google Ads data via Model Context Protocol, troubleshoot common setup issues, and start automating campaign analysis through direct API access.
Contents
Autonomous Marketing
Grow your business faster with AI agents
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
What is Claude Desktop MCP Google Ads integration?
Claude Desktop MCP Google Ads configuration guide connects Anthropic’s Claude AI directly to your Google Ads account via the Model Context Protocol (MCP). Instead of exporting CSVs and uploading them manually, Claude pulls live campaign data, performance metrics, and account insights through the Google Ads API in real-time. When properly configured, Claude can analyze your campaigns, detect underperformers, and recommend optimizations based on current data — not stale spreadsheet exports.
MCP is Anthropic’s open standard that allows Claude to securely connect to external data sources. The protocol acts as a bridge between Claude’s AI capabilities and Google’s advertising platform, enabling natural language queries like “Which campaigns had CPA > $50 this week?” or “Show me search terms with conversion rate < 2%.” According to Google, advertisers using API-driven optimization see 15-25% better performance than those relying on manual management alone.
The Claude Desktop MCP Google Ads configuration guide covers three setup methods ranging from no-code managed solutions to self-hosted Python implementations. Setup time varies from 2 minutes (managed) to 20 minutes (self-hosted), but all methods provide the same core capability: live Google Ads data accessible through conversational AI. This configuration is essential for marketers managing accounts with $10K+ monthly spend who need faster insights than manual reporting provides.
1,000+ Marketers Use Ryze
Automating hundreds of agencies
★★★★★4.9/5
What do you need to configure Claude Desktop MCP Google Ads?
Before starting the Claude Desktop MCP Google Ads configuration guide, verify you have the required software, accounts, and permissions. Missing prerequisites cause 80% of setup failures, so checking requirements first saves troubleshooting time later.
Software Requirements
- •Claude Desktop Application: Download from claude.ai/desktop. Web version does NOT support MCP servers.
- •Node.js 18+: Required for managed MCP connectors. Install from nodejs.org if using Ryze or similar services.
- •Python 3.8+: Needed only for self-hosted MCP servers. Include pip package manager.
- •Text Editor: For editing claude_desktop_config.json file. VS Code, Notepad++, or system default work.
Account Requirements
- •Claude Pro Subscription: $20/month. Free Claude accounts cannot connect MCP servers.
- •Google Ads Account: With active campaigns and historical data. Test accounts work for setup verification.
- •Google Cloud Project: Required for self-hosted setup only. Free tier sufficient for API credentials.
- •Admin Access: To Google Ads account for OAuth authentication. Standard users can view but not connect APIs.
Important: Account Permissions
Google Ads API access requires account admin permissions. Manager accounts (MCCs) need additional customer ID configuration. Verify your access level in Google Ads > Admin > Account Access before starting setup.
Configuration File Locations
The Claude Desktop MCP Google Ads configuration guide requires editing your claude_desktop_config.json file. File locations vary by operating system:
Create this file if it doesn’t exist. Ensure proper JSON syntax — trailing commas and mismatched brackets cause configuration errors.
What are the 3 ways to configure Claude Desktop MCP Google Ads?
Three methods exist for Claude Desktop MCP Google Ads configuration, each with different complexity levels, maintenance requirements, and cost structures. Choose based on your technical comfort level and control preferences.
| Method | Setup Time | Technical Level | Maintenance | Cost |
|---|---|---|---|---|
| Ryze MCP Connector | 2 minutes | Beginner | Fully managed | Free trial + subscription |
| Adspirer/CData Connector | 5-8 minutes | Intermediate | Semi-managed | $49-99/month |
| Self-hosted Python MCP | 15-20 minutes | Advanced | Self-managed | Free (Google API costs apply) |
Method 1: Ryze MCP Connector (Recommended)
The Ryze approach handles OAuth authentication, token refresh, and MCP server hosting automatically. Sign up at get-ryze.ai/mcp, connect your Google Ads account via OAuth, copy the provided configuration snippet, and paste it into your claude_desktop_config.json file. Total time: under 2 minutes. Best for marketers who want immediate results without technical overhead.
Method 2: Third-Party MCP Connectors
Services like Adspirer (listed in Claude Desktop’s official connector directory) and CData Code Assist provide hosted MCP endpoints. You authenticate your Google Ads account through their platform, then configure Claude to connect to their MCP server. Setup involves OAuth flows and configuration wizards but requires no local Python installations. Monthly subscription fees range from $49-99 depending on features and account limits.
Method 3: Self-Hosted Python MCP Server
For maximum control and zero ongoing costs, install Google’s official experimental MCP server from GitHub. This method requires creating a Google Cloud project, generating API credentials, setting up OAuth for your developer token, and configuring a local Python server. You maintain full control over data access and can customize the MCP server functionality, but you’re responsible for updates, security, and troubleshooting.
Ryze AI — Autonomous Marketing
Skip the configuration — let AI optimize your Google Ads 24/7
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
2,000+
Marketers
$500M+
Ad spend
23
Countries
How to configure Claude Desktop MCP Google Ads step by step
This walkthrough uses the Ryze MCP Connector method for fastest setup. For other methods, see the OpenClaw Google Ads Setup Guide (self-hosted) or refer to your chosen provider’s documentation.
Step 01
Install Claude Desktop
Download Claude Desktop from claude.ai/desktop. The web version does not support MCP servers. Install the application and sign in with your Claude Pro account ($20/month subscription required). Verify you can open the application and see the main chat interface before proceeding.
Windows users: Run the installer as Administrator if you encounter permission errors during installation.
Step 02
Create Ryze AI account and connect Google Ads
Visit get-ryze.ai/mcp and create a free account. In the dashboard, click “Connect Google Ads” and authenticate with your Google account. Grant read-only access to campaigns, ad groups, keywords, and reporting data. The OAuth flow completes in 30-60 seconds.
MCC accounts: Select the specific customer account you want to analyze during authentication, or configure multiple accounts later in the dashboard.
Step 03
Locate your Claude configuration file
Find your claude_desktop_config.json file using your operating system’s file path. If the file doesn’t exist, create it as a plain text file with the exact name.
Create the Claude folder if it doesn’t exist. The configuration file must be named exactly claude_desktop_config.json with proper capitalization.
Step 04
Configure the MCP server connection
Copy the MCP configuration snippet from your Ryze dashboard and paste it into claude_desktop_config.json. The configuration includes your API key and Google Ads customer ID automatically.
Save the file and ensure proper JSON syntax. No trailing commas, matching brackets, and quoted strings. Invalid JSON prevents Claude from loading MCP servers.
Step 05
Restart Claude Desktop and verify connection
Completely quit Claude Desktop and reopen it. Look for a small green indicator (hammer icon) near the message input box — this confirms MCP servers are loaded. If the indicator is red or missing, check your configuration file syntax and restart again.
Node.js required: If you see “npx command not found” errors, install Node.js 18+ from nodejs.org and restart Claude Desktop.
Step 06
Test the connection with a query
Send Claude a test message: “Show me my Google Ads performance for the last 7 days.” If the MCP connection works correctly, Claude returns a table with campaign names, impressions, clicks, cost, conversions, and other metrics pulled from your live Google Ads account.
Success Indicators
Claude responds with actual campaign data, not file upload requests. Metrics match your Google Ads dashboard. Response time under 30 seconds for typical queries.
How does OAuth authentication work for Claude Desktop MCP Google Ads?
OAuth authentication ensures secure access to your Google Ads data without exposing account passwords. The Claude Desktop MCP Google Ads configuration guide uses OAuth 2.0 flows to generate temporary access tokens that can read your campaign data but cannot make changes. Understanding this process helps troubleshoot authentication errors and configure multiple accounts.
OAuth Flow Steps
Authorization Request
Click “Connect Google Ads” in your MCP service dashboard. This redirects you to Google’s authorization server with your application’s client ID and requested permissions scope.
User Consent
Google displays permission requests for your Google Ads account. Review and approve read access to campaigns, keywords, and reporting data. No write permissions are requested.
Authorization Code
Google generates a temporary authorization code and redirects back to the MCP service. This code expires in 10 minutes and can only be used once.
Access Token Exchange
The MCP service exchanges the authorization code for an access token and refresh token. These tokens enable API calls on your behalf without password exposure.
Token Management and Security
Access tokens expire after 1 hour but refresh tokens remain valid until explicitly revoked. Managed MCP services handle token refresh automatically — you never see or manage tokens directly. For self-hosted setups, you’re responsible for implementing refresh logic in your MCP server code.
- •Scope Limitations: Tokens only access Google Ads data, not Gmail, Drive, or other Google services.
- •Read-Only Access: Cannot create campaigns, change bids, or modify account settings.
- •Revocation: Revoke access anytime through Google Account settings > Security > Third-party apps.
- •Account Isolation: Each Google Ads account requires separate OAuth authorization.
Manager Account (MCC) Considerations
MCC accounts require additional customer ID configuration. During OAuth, specify which child account to access. Some MCP services support multiple accounts under one OAuth flow, while others require separate authentications for each account.
How to fix common Claude Desktop MCP Google Ads setup errors?
Most Claude Desktop MCP Google Ads configuration errors stem from JSON syntax mistakes, missing software dependencies, or incorrect OAuth settings. These solutions fix 95% of reported setup issues.
Error: MCP server not connected / No green indicator
Claude Desktop shows red MCP indicator or no indicator. Queries return “I need you to upload a file” instead of live data.
Solutions:
- 1.Check claude_desktop_config.json syntax — remove trailing commas and verify bracket matching
- 2.Ensure Node.js 18+ is installed (for npx-based connectors like Ryze)
- 3.Completely quit and restart Claude Desktop application
- 4.Verify file path — config file must be in exact location for your OS
Error: “Authentication failed” or “Invalid credentials”
Claude connects to MCP server but cannot access Google Ads data. API key or OAuth token issues.
Solutions:
- 1.Re-authenticate Google Ads in your MCP service dashboard
- 2.Verify Google Ads API access is enabled (Tools & Settings > API Center)
- 3.Check customer ID format — numbers only, no dashes (1234567890 not 123-456-7890)
- 4.For MCC accounts, specify correct child customer ID in configuration
Error: “npx command not found” (Windows/Mac/Linux)
Claude tries to launch MCP server but npx executable is missing. Affects Ryze and similar npx-based connectors.
Solutions:
- 1.Install Node.js 18+ from nodejs.org (includes npx automatically)
- 2.Restart terminal/command prompt after Node.js installation
- 3.Test npx works: open terminal, run “npx --version”
- 4.Restart Claude Desktop after confirming npx installation
Error: “Permission denied” or “Insufficient access level”
OAuth succeeded but Google Ads account lacks API access permissions. Common in enterprise/agency accounts.
Solutions:
- 1.Request admin access to Google Ads account from account owner
- 2.Enable API access in Google Ads: Tools & Settings > Setup > API Center
- 3.For enterprise accounts, contact Google Ads support for API approval
- 4.Test with a different Google Ads account with confirmed API access
Error: Slow responses or timeouts
Claude takes > 30 seconds to respond or shows timeout errors. MCP server or API connection issues.
Solutions:
- 1.Check internet connection and firewall settings
- 2.Reduce query complexity — ask for specific campaigns or shorter time periods
- 3.Restart MCP server by restarting Claude Desktop
- 4.Contact MCP service provider if using managed solution
Sarah K.
Paid Media Manager
E-commerce Agency
Setting up Claude MCP for Google Ads took 3 minutes with Ryze. Now I get instant answers about campaign performance instead of building reports for hours. Game changer.”
3 min
Setup time
90%
Time saved
Live
Data access
How to test your Claude Desktop MCP Google Ads connection?
Testing verifies your Claude Desktop MCP Google Ads configuration works correctly and returns accurate data. Start with simple queries, then progress to complex analysis to confirm full functionality.
Basic Connection Test
Send this exact message to Claude: “List my Google Ads accounts.” A successful response shows your account name(s), customer ID(s), and account status. If Claude asks you to upload a file instead, the MCP connection failed.
✓ Expected Response
Returns table with account names, customer IDs, currency, timezone. Response time < 10 seconds.
✗ Failed Response
“Please upload a CSV file” or “I need access to your data.” MCP server not connected.
Campaign Data Test
Test live data access: “Show me my campaign performance for the last 30 days including impressions, clicks, cost, and conversions.” Cross-reference the results with your Google Ads dashboard to verify accuracy.
Advanced Query Test
Verify complex analysis capability: “Analyze my search terms report for the last 30 days. Show me search terms with > 100 impressions but < 2% conversion rate. Group by campaign and suggest negative keyword recommendations.”
- •Data Freshness: Confirm metrics match your Google Ads dashboard within 1-2 hours
- •Analysis Depth: Claude should provide insights, not just data dumps
- •Response Speed: Complex queries should complete within 60 seconds
- •Error Handling: Graceful responses for date ranges with no data
Pro Tip: Performance Benchmarking
Save a few test queries as benchmarks. Run them periodically to verify your MCP connection stays healthy. Performance degradation often indicates token expiration or configuration drift.
Frequently asked questions
Q: Does Claude Desktop MCP Google Ads work with free Claude accounts?
No. MCP server connections require Claude Pro subscription ($20/month). Free accounts cannot connect to external data sources via MCP protocol.
Q: Can Claude make changes to my Google Ads campaigns?
No. Claude Desktop MCP Google Ads configuration provides read-only access. It can analyze data and recommend changes but cannot modify campaigns, bids, or budgets.
Q: Which method is fastest for Claude Desktop MCP Google Ads setup?
Ryze MCP Connector takes under 2 minutes. Create account, authenticate Google Ads, copy configuration to Claude. No technical setup required.
Q: Does this work with Manager (MCC) accounts?
Yes, but requires specifying customer IDs for child accounts. Some MCP services support multiple accounts, others need separate authentication for each account.
Q: How fresh is the Google Ads data in Claude?
MCP connections pull live data from Google Ads API. Metrics are typically 1-3 hours behind real-time due to Google’s data processing delays, not the MCP connection.
Q: What happens if my Google Ads OAuth token expires?
Managed MCP services handle token refresh automatically. Self-hosted setups require implementing refresh logic. Expired tokens cause authentication errors until refreshed.
Ryze AI — Autonomous Marketing
Configure Claude Desktop MCP Google Ads in under 2 minutes
- ✓Automates Google, Meta + 5 more platforms
- ✓Handles your SEO end to end
- ✓Upgrades your website to convert better
2,000+
Marketers
$500M+
Ad spend
23
Countries
Related guides
Google Ads
How to Use Claude for Google Ads
Complete guide to Claude AI for Google Ads optimization, analysis, and automation workflows.
Skills
15 Claude Skills for Google Ads
Specific Claude prompts and skills for Google Ads campaign management and optimization.
Self-hosted
OpenClaw Google Ads Setup Guide
Self-hosted open-source MCP server configuration for Google Ads integration.
Comparison
Top AI Tools for Google Ads 2026
Compare Claude, Ryze AI, and other AI tools for Google Ads management and optimization.
