Camberstack: a Google Ads MCP server

Connect Google Ads (and, optionally, Search Console) to Claude, ChatGPT, Cursor or any MCP client. Your AI reads the account with read-only tools and can propose changes, from negative keywords to whole campaigns. Nothing changes in the account until you approve a specific proposal, and every applied change can be undone.

Hosted: https://camberstack.io/mcp (Free: 1 Google Ads account, every tool, unlimited changes; Pro $15/mo: up to 10 accounts). Setup: https://camberstack.io/#setup

Tools

The Search Console tools take either days or exact start_date/end_date, and fresh: true to include the last 2-3 days Google is still filling in. Requesting indexing and submitting sitemaps aren't available: Camberstack only holds the read-only scope. | paid_organic_overlap | no | joins an Ads account's search terms with a site's organic queries: searches paid for that already rank near the top, and page-2+ searches with no ad | | propose_changes | no | resolves changes against the live account, dry-runs them with Google (validateOnly), stores a proposal with a plain-English summary | | apply_changes | yes | applies a stored proposal (the user's own, un-applied, under 24h old); records each change's inverse | | undo_changes | no | builds the reversing proposal for an applied one | | billing | no | plan, Google Ads accounts in use (last 30 days) vs. the plan's limit, and a personal upgrade or manage-billing link | | discard_proposal, change_history, disconnect | | |

What a proposal can do:

• Control: add negative keywords; pause or enable a campaign, ad group, keyword or ad; set a campaign's daily budget (never a shared budget) or its end date.
• Build: create a whole Search campaign (ad groups, keywords, responsive search ads, targeting, negatives, sitelinks), always created paused; add an ad group, keywords, an ad or sitelinks to an existing campaign.
• Tune: keyword and ad group bids, bid strategy, location and language targeting, presence-only location mode, final URL suffix.
• Measure: create a conversion action, set its counting, scope a campaign to one conversion goal.

Risky changes carry a ⚠ line in the proposal summary: enabling a campaign, more than doubling a budget or a bid, switching bid strategy, removing the last location, a new primary conversion action. Undo removes only what Camberstack itself created; nothing the user built is ever deleted. Search Console is read-only.

How auth works

Camberstack is an OAuth 2.1 authorization server for MCP clients (dynamic client registration, PKCE). Its /authorize sends the user to Google for adwords + openid email, plus webmasters.readonly (Search Console), which the user may untick: only adwords is required. The Google refresh token is stored AES-256-GCM encrypted and never leaves the server. The MCP client gets Camberstack's own tokens, which are stored only as SHA-256 hashes.

Two MCP SDKs, on purpose: /mcp is served by SDK v2 (@modelcontextprotocol/server + /node), which answers both 2026-07-28 clients (server/discover) and 2025-era ones (initialize, kept on a JSON-response transport). The authorization server (mcpAuthRouter, requireBearerAuth) stays on @modelcontextprotocol/sdk 1.x, because v2 ships only the resource-server half. Don't drop 1.x until v2 (or a companion package) has /authorize, /token and /register.

Run it

npm ci && npm test
ENCRYPTION_KEY=$(openssl rand -hex 32) \
GOOGLE_CLIENT_ID=… GOOGLE_CLIENT_SECRET=… GOOGLE_ADS_DEVELOPER_TOKEN=… \
BASE_URL=https://your.host npm run dev

scripts/try-account.ts runs the read tools against a real account from an existing refresh token, skipping OAuth. Use it for dogfooding.

License

MIT