AdvisorPPC
Sign in Start free
Menu

Documentation

AdvisorPPC connector docs

AdvisorPPC is a hosted Model Context Protocol connector. You authorize your own Google accounts once, then ask an AI assistant to audit campaigns, find wasted ad spend, and report on performance in plain language. Every answer comes from the official Google APIs, running as you.

Brushed aluminium surface with a green performance curve rising from lower left to upper right

Claude MCP endpoint https://chatgpt-mcp.advisorppc.com/claude

New here? The getting started guide connects AdvisorPPC to Claude in about two minutes, with no API key to copy.

What is AdvisorPPC?

A connector, not an agency and not another dashboard. It gives an AI assistant a safe, authorized path into the advertising and analytics accounts you already own:

  • Google Ads. Account audits, wasted spend analysis, search term mining, negative keywords, recommendations, change history, and campaign and budget management on paid plans.
  • Google Analytics 4. Reporting on traffic, conversions, and the channels feeding your paid campaigns.
  • Google Search Console. Query, page, and index coverage data next to the paid picture.
  • Google Tag Manager. Container inspection, so you can check that conversion tracking is actually wired up.
  • YouTube. Channel and video performance for the video side of the account.

The capabilities reference describes each area in detail.

Who is it for?

People who are accountable for paid search results and would rather ask a question than build a report. AI PPC management here means the assistant does the fetching, the reading, and the arithmetic, and you decide what changes.

In-house marketers

Run a PPC audit before a budget review, and get a straight answer on where the money went last month.

Agencies and consultants

Work across client accounts from one assistant, with each account authorized separately and every action logged.

Business owners

Check whether an account is healthy without learning the Google Ads interface first.

Developers and AI builders

Add a maintained Google Ads MCP surface to an agent instead of writing and refreshing OAuth plumbing yourself.

Where do I go next?

Getting started

Connect from claude.ai, the Claude desktop app, or Claude Code, then link your Google account and try your first prompts.

Connect AdvisorPPC

Capabilities

What the connector can do in each area, from Google Ads audits to Tag Manager inspection.

Read the reference

Plans and limits

The free read-only tier, what paid plans unlock, and how monthly call quotas are enforced.

Compare plans

Security

OAuth 2.1 in your own browser, no API keys in config files, and server-side gating on every write.

How access works

ChatGPT

Add AdvisorPPC as a developer-mode connector in ChatGPT and complete the same OAuth flow.

ChatGPT setup

Grok

Point Grok at the dedicated AdvisorPPC endpoint built for it.

Grok setup

Troubleshooting

The failures people actually hit, including the 401 you get from opening the MCP endpoint in a browser.

Fix a problem

Support

How to reach a human, what to include so the first reply is useful, and how to report a security issue.

Get help

Setup by AI client

Paste the hosted endpoint for your client, then finish OAuth in the browser. Claude and ChatGPT register themselves. Cursor and generic clients may ask for generated credentials.

Hosted remote MCP versus local configuration

Claude, ChatGPT, and Grok use a hosted remote MCP URL. You paste that URL in the client's connector settings and finish OAuth in the browser. Cursor and some generic clients also accept that hosted URL, but they may ask you to edit a local MCP config file. Local or CLI steps never replace the browser OAuth screen, and they never need a Google or Meta password.

Claude and ChatGPT register their own OAuth client. Do not generate a dashboard Client ID and Secret for those two. Use generated credentials only when a client asks for them, typically Cursor or a generic MCP client without dynamic registration.

1. Add the connector in Claude

  1. In Claude, open Settings > Connectors > Add custom connector.
  2. Paste the endpoint below and confirm.
  3. Claude registers itself automatically (OAuth 2.1 dynamic client registration); no client ID or secret to copy.
  4. Sign in or create your AdvisorPPC account when the consent screen opens, then approve the connection.
Claude MCP endpoint https://chatgpt-mcp.advisorppc.com/mcp

Connect AdvisorPPC to ChatGPT

  1. In ChatGPT, open Settings > Connectors / Apps and add a custom connector.
  2. Paste the ChatGPT endpoint below. Leave advanced client fields empty: ChatGPT registers itself.
  3. Complete AdvisorPPC OAuth in the browser. Create an account or sign in there if needed.
  4. Return to ChatGPT and start with a read-only account list before asking for a change.

This is hosted remote MCP setup. A public ChatGPT app listing is not claimed here.

ChatGPT MCP endpoint https://chatgpt-mcp.advisorppc.com/mcp

Connect AdvisorPPC to Grok

  1. On grok.com, open Connectors > New Connector > Custom.
  2. Paste the Grok endpoint below.
  3. Finish the AdvisorPPC OAuth screen in the browser.
  4. Authorize Google Ads (and any other entitled platforms) in AdvisorPPC Settings, then return to Grok.

This is generic custom-connector guidance for the hosted /grok endpoint, not an official Grok marketplace listing.

Grok MCP endpoint https://chatgpt-mcp.advisorppc.com/grok

Connect AdvisorPPC to Cursor

  1. In Cursor, open Settings > MCP > Add custom MCP server.
  2. Use the hosted remote URL below with Streamable HTTP. This is not a local stdio binary.
  3. If Cursor opens a browser consent screen, sign in to AdvisorPPC and approve access there.
  4. If Cursor asks for an OAuth Client ID and Secret, generate them under Settings, then MCP connectors. Claude and ChatGPT never need these.

Cursor configuration can live in the UI or in a local MCP config file. Both still use the hosted endpoint. Do not paste provider passwords into Cursor.

Cursor MCP endpoint https://chatgpt-mcp.advisorppc.com/mcp

Connect AdvisorPPC to Gemini

  1. Install the Gemini CLI (or use Gemini Code Assist), then run the command below in a terminal. It registers the hosted endpoint over Streamable HTTP.
  2. Run gemini mcp add -t http advisorppc https://chatgpt-mcp.advisorppc.com/mcp
  3. Start Gemini and approve the AdvisorPPC OAuth screen in the browser. Sign in or create your account there.
  4. If your Gemini client asks for a Client ID and Secret, generate them under Settings, then MCP connectors.

The Gemini consumer app does not take custom connectors today; the Gemini CLI and Code Assist do. Same account, same plan, same connected ad platforms as every other host.

Gemini MCP endpoint https://chatgpt-mcp.advisorppc.com/mcp

Connect a generic MCP-compatible client

  1. In your MCP-compatible client, add a custom remote server that speaks Streamable HTTP.
  2. Paste the generic endpoint below. Do not use a local stdio command unless your client documents that separately.
  3. If the client supports OAuth 2.1 dynamic registration, it registers itself and opens the browser consent screen.
  4. If it asks for a Client ID and Secret, generate them in Settings. Never generate those for Claude or ChatGPT.

This is setup guidance for MCP-compatible clients. It is not a guarantee that every client, plugin, or marketplace listing will work.

Generic MCP client MCP endpoint https://chatgpt-mcp.advisorppc.com/mcp
AdvisorPPC workflow paths reaching a verified approval control
OAuth-authorized data paths with a verified connection

The short version

  • No API keys. Authorization happens in your own browser over OAuth 2.1, and tokens stay on our servers.
  • Free to start. Standard Free access is read-only: 20 Google Ads API requests and 100 cached or local report reads per month.
  • Your accounts, your permissions. The connector can only reach accounts you authorized, through official Google APIs.
  • Reversible. Remove the connector, or revoke access from your Google account permissions, and it stops immediately.