Troubleshooting

The connector URL shows 401 Unauthorized in my browser

This is expected. Nothing is broken.

Opening https://mcp.advisorppc.com/claude in a browser tab returns 401 Unauthorized because it is an MCP protocol endpoint for an AI client, not a web page. It has no HTML to serve and it refuses unauthenticated requests by design. The same is true of the ChatGPT and Grok endpoints.

Paste the URL into your assistant's Add custom connector field instead. If you want a page you can read in a browser, you are already on it: the documentation is the human facing side of this service.

The connector shows as disconnected

Remove the connector and add it again.

Re-adding runs a fresh OAuth flow and registers a new client. That is the single fix for most connection states, because it clears an approval that expired, a registration left over from an earlier attempt, and a client that was never fully bound to your account. It costs about thirty seconds and never touches your Google authorization, so you do not have to reconnect your ad accounts afterwards.

Before re-adding, confirm the endpoint is exactly right, with no trailing characters and no path added. The correct values are on the getting started, ChatGPT, and Grok pages.

This client_id belongs to a different account

Re-add the connector so a fresh client is registered.

Each registered client is claimed by the first AdvisorPPC account that approves it, and it stays bound to that account. If you signed in with a different email, or someone else approved the connection on a shared machine, the client is bound elsewhere and cannot be reassigned. Removing and re-adding the connector registers a new client, which then binds to whichever account approves it.

When you re-approve, check the email shown on the consent screen. Binding to the wrong account is almost always a second sign-in address rather than a fault in the connector.

A tool call was denied on the free plan

Either the monthly allowance is used up, or the tool is paid-only.

Check the reason in the response and the current access shown in your workspace:

• A report allowance is exhausted. Standard Free access includes 20 Google Ads API requests and 100 cached or local report reads per month. Discovery, pages and retries each count as API requests. Reuse a fresh cached report when available, or check the remaining allowance and renewal in your workspace.
• The tool changes an account. Free is read-only. A client may list write tools, but AdvisorPPC refuses a call without the appropriate paid entitlement and Google permissions.
• The tool reads another Google service. GA4, Tag Manager, Search Console and YouTube also require the appropriate paid access. Free provider access covers Google Ads reads.

Missing plan access is checked before the operation runs. Free Ads allowance is checked before each API attempt, so a report can exhaust it after earlier pages or retries have run. For a write with an unknown provider outcome, inspect its receipt and the account before retrying. See plans and limits.

The assistant cannot see any of my accounts

Connecting the connector and authorizing Google are two separate steps.

Approving the AdvisorPPC consent screen proves who you are. It does not grant access to any advertising account. Open dashboard settings and connect Google, then check that the accounts you expect were included in the consent screen. If you manage clients under a Google Ads manager account, authorize the manager account so the accounts beneath it become reachable.

Where do I get help?

If none of the above fixes it, email technical support at support@advisorppc.com. Include what you asked the assistant, which plan you are on, and roughly when it happened with your time zone. The support page lists everything worth sending so the first reply can be a fix rather than a question.

Billing, plan and partnership questions go to contact@advisorppc.com instead, and security reports go to that same address with SECURITY in the subject line.