Google Ads vs GEO MCP

A side-by-side look at the Google Ads and GEO MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Google Ads logoGoogle AdsMarketing · Local subprocess (stdio)Google Ads: 31 read tools with full Keyword Planner, 7 write tools that preview first.55GoodAuth: not declaredGEO MCP logoGEO MCPMarketing · Remote HTTP/SSEGoogle Ads, Meta Ads, SEO, GEO & GA4 MCP by Ryze AI - audits, reports, keywords, Search Console.48FairAuth: not declared

Verdict: choose Google Ads for marketing work as a local process; choose GEO MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Google Ads logoChoose Google Ads when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN, GOOGLE_ADS_LOGIN_CUSTOMER_ID.
  • You want tools like google_ads_list_accounts, google_ads_get_account_details, google_ads_run_gaql.
Explore Google Ads

GEO MCP logoChoose GEO MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
Explore GEO MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Ads logoGoogle AdsGEO MCP logoGEO MCP
CategoryMarketingMarketing
Quality signal55/100 · Good48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsGOOGLE_ADS_DEVELOPER_TOKENGOOGLE_ADS_CLIENT_IDGOOGLE_ADS_CLIENT_SECRETGOOGLE_ADS_REFRESH_TOKENGOOGLE_ADS_LOGIN_CUSTOMER_IDNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars15,505
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools45Not listed

Tools & capabilities

Google Ads tools 45

  • google_ads_list_accountsList Google Ads customer accounts accessible with the current credentials.
  • google_ads_get_account_detailsGet detailed information for a specific Google Ads customer account.
  • google_ads_run_gaqlExecute a raw GAQL (Google Ads Query Language) query.
  • google_ads_get_insightsQuery Google Ads performance insights with intelligent query planning.
  • google_ads_get_campaignsList campaigns for a Google Ads account with status, budget, channel type, and bidding strategy.
  • google_ads_get_adgroupsList ad groups for a Google Ads account, optionally filtered by campaign.
  • google_ads_get_keyword_performanceGet keyword-level performance data from keyword_view resource.
  • google_ads_validate_queryValidate metric/dimension/resource compatibility BEFORE executing a query.
  • google_ads_health_checkRead-only connectivity check.
  • google_ads_get_account_hierarchyList accessible customers and, where possible, manager/client relationships from GAQL customer_client.
  • google_ads_get_conversion_actionsList conversion actions with status, type, category, primary/include-in-conversions flags, owner customer, and last activity dates when supported.
  • google_ads_get_change_eventsFetch recent change_event rows.
  • +33 more on the listing page

GEO MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Google Ads

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "google-ads-6": {
      "command": "npx",
      "args": [
        "-y",
        "@getmcpads/google-ads-mcp-server"
      ],
      "env": {
        "GOOGLE_ADS_DEVELOPER_TOKEN": "YOUR_GOOGLE_ADS_DEVELOPER_TOKEN_HERE",
        "GOOGLE_ADS_CLIENT_ID": "YOUR_GOOGLE_ADS_CLIENT_ID_HERE",
        "GOOGLE_ADS_CLIENT_SECRET": "YOUR_GOOGLE_ADS_CLIENT_SECRET_HERE",
        "GOOGLE_ADS_REFRESH_TOKEN": "YOUR_GOOGLE_ADS_REFRESH_TOKEN_HERE",
        "GOOGLE_ADS_LOGIN_CUSTOMER_ID": "YOUR_GOOGLE_ADS_LOGIN_CUSTOMER_ID_HERE"
      }
    }
  }
}

GEO MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "google-ads-meta-ads-seo-geo-mcp": {
      "url": "https://connector.get-ryze.ai/mcp"
    }
  }
}

Frequently asked questions

Google Ads is categorized under Marketing and uses a local stdio subprocess. GEO MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick Google Ads for marketing work and GEO MCP for marketing.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Google Ads has no declared pricing — check the project's own site. GEO MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add google-ads-6 and google-ads-meta-ads-seo-geo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Ads has a quality signal of 55/100 (Good) with 1 views, 0 installs and 1 GitHub stars. GEO MCP has 48/100 (Fair) with 1 views, 0 installs and 5,505 GitHub stars.