Home/PaidHelm documentation
Getting started
PaidHelm documentation
Everything you need to connect an AI assistant to Google Ads through PaidHelm: setup per client, authentication, the full tool catalog, plans and quotas, and troubleshooting.
PaidHelm is a remote MCP server. Your assistant connects to https://mcp.paidhelm.com/googleads/mcp over HTTPS, you sign in with Google once, and from then on the assistant can call the tools listed in this documentation on your Google Ads accounts.
https://mcp.paidhelm.com/googleads/mcpServer URL (Streamable HTTP)
https://mcp.paidhelm.com/googleads/sseLegacy SSE transport
OAuth 2.0Dynamic client registration + PKCE
Start here
- Quickstart: connect in five minutes with Claude, then run your first report.
- Connecting your Google Ads account: which Google login to use, manager accounts, multiple clients.
- Client setup: configuration for every supported assistant and IDE.
Reference
- Tool catalog: all 32 tools with parameters and examples.
- Reports and GAQL: how the assistant queries any Google Ads report.
- Creating campaigns: Search, Performance Max, Display, Demand Gen, Shopping and App.
- Keywords and negatives, Bidding and budgets.
- Plans and tasks: how quotas are counted and how to upgrade from the chat.
- Authentication and security: OAuth flow, scopes, token storage, revocation.
- Prompt library: proven prompts for audits, reports and builds.
- Troubleshooting and FAQ.
For LLMs and agents
This documentation is also available as plain text: /llms.txt (index) and /llms-full.txt (full content). Each page has a Markdown version at index.md under the same URL.