Google Ads vs Google Adwords

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

G
Google AdsMarketing · Remote HTTP/SSE
Google Ads reporting and campaign management. Everything it creates starts paused.39FairAuth: oauth 2.0
Google Adwords logoGoogle AdwordsMarketingMCP server for Google Ads campaign and budget management32EmergingAuth: not declared

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

Which MCP server should you choose?

G
Choose Google Ads when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Google Ads

Google Adwords logoChoose Google Adwords when

  • You need dedicated capabilities in the Marketing domain.
Explore Google Adwords

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
G
Google Ads
Google Adwords logoGoogle Adwords
CategoryMarketingMarketing
Quality signal39/100 · Fair32/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—0
Directory activity 0 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Google Ads tools

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

Google Adwords 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": {
      "command": "npx",
      "args": [
        "-y",
        "google-ads"
      ]
    }
  }
}

Google Adwords

No confirmed install command for Google Adwords yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Google Ads is categorized under Marketing and uses a remote HTTP/SSE transport. Google Adwords belongs to Marketing and uses an install path we have not confirmed yet. Pick Google Ads for marketing work and Google Adwords 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 Adwords has no confirmed install command yet — follow its own setup instructions.

Google Ads has no declared pricing — check the project's own site. Auth: oauth 2.0. Google Adwords 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 and google-adwords 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 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Google Adwords has 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.