v2.0.0: Native tools, security and product demo

Google Ads now has a documented standalone source release with 35 read tools and 10 optional write tools.

Highlights

• Add descending image/video asset pagination.
• Add account-scoped upload processing reads and return the native upload ID.
• Retain API v25, standalone MCC discovery and credential redirect protection.
• Require Node.js 22.12 or newer and check Node 22/24 in CI.
• Update vulnerable dependencies and regenerate the MCP catalog.

Since the previous published GitHub release

This release also includes the v1.1 source updates: native platform tools, MCP annotations, parameter descriptions, structured results and a generated discovery card. Those changes were previously in the repository but not in its latest published GitHub release. See the complete changelog.

Documentation and demo

The README now opens with the homepage product film, version highlights, source installation and a complete tool reference. The film shows hosted getmcpads with staged data; hosted creative integrations and MCP Apps UI are not included in this standalone release.

Compatibility and installation

Requires Node.js 22.12 or newer. Node 18 and 20 are no longer supported. Inspect the current tool schemas before reusing saved calls.

Distribution: this publishes the GitHub source release. npm and MCP Registry publication are separate steps.

git clone --branch v2.0.0 --depth 1 https://github.com/getmcpads-com/google-ads-mcp-server.git
cd google-ads-mcp-server
npm ci
npm run build

Configure your client to run node with the absolute path to dist/cli.js and your platform credentials.

Validation

The implementation passed typecheck, lint, build, offline tests and GitHub CI on Node 22 and 24. The dependency audit reported zero known vulnerabilities on September 20, 2026. No live advertising write was performed.

Watch the product film · Read the documentation · Explore hosted getmcpads

Maintained by Emmanuel, getmcpads. Contact: hello@getmcpads.com.

v1.0.2

Fixes the version each server announced over MCP: it introduced itself as 1.0.0 while shipping 1.0.1, a small untruth repeated on every handshake.

A test now compares the literal in src/server.ts against package.json, so package.json, server.json and the announced version have to move together.

Install: npx -y @getmcpads/google-ads-mcp-server

v1.0.1

Listed in the MCP Registry as com.getmcpads/google-ads.

• server.json and mcpName, so the registry can verify package ownership
• npm homepage now points at the product page rather than back at this README
• a workflow that republishes to the registry on each version tag, and refuses to run when the tag, package.json and server.json disagree

Install: npx -y @getmcpads/google-ads-mcp-server