PaidHelm for Google Ads

com.paidhelmPublished by paidhelm.comOfficial publisherv1.0.1Updated Nov 4, 2026

Google Ads reports, audits, negatives, bidding and campaign builds from Claude, ChatGPT or Cursor.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant work with Google Ads: pull reports, run audits, manage negative keywords, adjust bidding and build campaigns.

What you can do
  • Pull Google Ads reports and performance data
  • Run account audits
  • Manage negative keywords
  • Adjust bidding settings
  • Build campaigns
  • All actions are driven from an assistant such as Claude, ChatGPT or Cursor.
When to use it
Useful when you manage Google Ads accounts and want an assistant to review performance, audit accounts, or make changes to negatives, bids and campaigns without switching tools. Suited to marketers and agencies working inside a chat client.
Requirements
A remote MCP endpoint at mcp.paidhelm.com over streamable HTTP; no local package or environment variables. OAuth authentication is required, so a PaidHelm account and an authorized Google Ads connection are implied.
Before you install
The server can change live advertising accounts: negative keywords, bidding and campaign builds are write actions that may affect spend. Grant OAuth access only to accounts you intend to expose, and review changes before they go live. Account data is sent to the PaidHelm service.

Installation

In SourceWeft

  1. Open PaidHelm for Google Ads in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.paidhelm%2Fgoogle-ads/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "paidhelm-for-google-ads": {
      "type": "http",
      "url": "https://mcp.paidhelm.com/googleads"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 4, 2026
  2. v1.0.0Nov 3, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.