
Connects Claude to the Google Ads API through Pipeworx's gateway, exposing five core tools for campaign management and analysis. You get standard operations like listing campaigns and ad groups, pulling detailed campaign settings, and fetching performance metrics (impressions, clicks, cost, conversions) across date ranges. The standout is gads_search, which lets you run raw GAQL queries for custom filtering and aggregations. Supports both direct tool calls and natural language queries through ask_pipeworx. Useful when you need to audit account structure, compare campaign performance, or extract specific data slices without opening the Ads UI. Part of a larger gateway offering 673+ data sources if you need broader integration coverage.
Google Ads MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
gads_list_campaigns | List all campaigns in your Google Ads account. Returns campaign names, IDs, statuses, budgets, and types. Use to overview account structure or find a campaign ID for detailed analysis. |
gads_get_campaign | Get detailed settings for a specific campaign. Returns name, status, budget, bidding strategy, and configuration. Use to review or audit a campaign's current setup. |
gads_campaign_metrics | Get performance metrics for campaigns over a date range. Returns impressions, clicks, cost, conversions, CTR, and CPC. Use to analyze campaign effectiveness or compare performance trends. |
gads_list_ad_groups | List ad groups within a campaign by campaign ID. Returns ad group names, IDs, statuses, and CPC bids. Use to explore campaign structure or select an ad group for analysis. |
gads_search | Run custom GAQL queries against Google Ads data. Use for advanced analysis—filter by keywords, matching types, or aggregate metrics by custom dimensions. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"google_ads": {
"url": "https://gateway.pipeworx.io/google_ads/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/google_ads/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Google_ads data" })
The gateway picks the right tool and fills the arguments automatically.
MIT