Troubleshooting
Common issues and how to fix them. If you can't find your problem here, reach out via the link at the bottom of this page.
Watch the setup walkthrough first
Most install issues are resolved by following this 5-minute video exactly. It covers adding your first domain, connecting marketing data sources, and creating an API key. Watch it before diving into the fixes below.
Connection & Setup
Connector won't install or "Unable to connect to server"
Cause: The server URL is wrong, your network is blocking the outbound HTTPS connection, or the Agentcy endpoint is temporarily unreachable.
Fix: Verify the server URL is exactly https://data.goagentcy.com/mcp (not goagentcy.com/mcp, not HTTP). Check your network doesn't block outbound HTTPS. Retry after 60 seconds.
OAuth popup closes before completing sign-in
Cause: Browser popup blocker, third-party cookies disabled, or an ad-blocker is interfering with the OAuth callback.
Fix: Allow popups from data.goagentcy.com, enable third-party cookies for the OAuth flow, or try in an incognito window.
Agentcy connector shows but tools aren't available
Cause: The MCP client connected but tool discovery hasn't completed yet.
Fix: Disconnect and reconnect the Agentcy connector. If the issue persists, restart your MCP client.
Authentication
"Unauthorized" or "Invalid API key" error
Cause: API key is missing, expired, has whitespace, or doesn't match an active account.
Fix: Generate a fresh API key at app.goagentcy.com → Settings → API Keys. Copy it carefully — no leading/trailing spaces. All Agentcy keys start with agcy_.
API key worked yesterday, doesn't work today
Cause: Key was rotated, account was downgraded, or plan was cancelled.
Fix: Check app.goagentcy.com → Billing for account status. If the account is active, regenerate your API key.
No Data Returned
"Service not configured for this domain"
Cause: The data source (GA4, GSC, Ads, etc.) hasn't been connected to the domain yet.
Fix: Visit app.goagentcy.com → Domains, click the domain, and configure the service. For Google services (GA4, GSC, Ads), make sure you've authorized the correct Google account with the right scopes.
"Domain not found"
Cause: The domain hasn't been added to your Agentcy account yet.
Fix: Add the domain at app.goagentcy.com → Domains → Add domain. Use the bare domain (e.g., example.com), not a full URL.
Response says "no data available" but GA4 has data
Cause: The date range is too recent (GA4 has a 24-48 hour processing lag) or the configured property ID doesn't match.
Fix: Try asking for data from 2-3 days ago instead of today. Verify the GA4 property ID in the domain settings matches the property you expect data from.
Quota & Rate Limits
"Monthly query limit reached"
Cause: You've hit your plan's query quota for the billing period.
Fix: Upgrade your plan at app.goagentcy.com → Billing, or wait until your billing period resets. Query usage is visible at app.goagentcy.com → Usage.
"Rate limit exceeded" (429)
Cause: Too many queries sent in a short window (default: 60/min).
Fix: Wait 60 seconds and retry. If you need a higher rate limit for production workloads, contact support.
Data Source-Specific
Google Analytics 4 — "property not found" or "permission denied"
Cause: The connected Google account doesn't have access to the GA4 property, or the property ID is incorrect.
Fix: In GA4, verify your Google account has Viewer or higher access to the property. In Agentcy, reconfigure the GA4 service and select the correct property from the list.
Google Search Console — "site not verified" or empty results
Cause: The site URL in Agentcy doesn't match the verified property URL in Search Console exactly.
Fix: Copy the site URL format from Search Console exactly — including whether it uses https://, http://, www., or a Domain property (sc-domain:). The format must match precisely.
Google Ads — "customer not found" or MCC account issues
Cause: For accounts accessed through a Manager (MCC), Agentcy needs both the customer ID and the login_customer_id.
Fix: In the Google Ads domain config, enter both the customer ID (the account you want to query) and the login_customer_id (the MCC account you authenticate through). Format: no dashes.
WooCommerce — "unauthorized" or "invalid consumer key"
Cause: The consumer key/secret is expired or has insufficient permissions.
Fix: In WooCommerce → Settings → Advanced → REST API, generate a new key with Read permissions. Copy the consumer key and secret exactly into the Agentcy domain config.
SpyFu, Moz, or Nano Banana — "API key required"
Cause: These are BYOK (bring-your-own-key) services. You need to add your own API key at the account level.
Fix: Visit app.goagentcy.com → Services, enable the service, and paste your API key. Once configured, the service is available across all your domains automatically.
Still stuck?
If your issue isn't covered here, reach out with a clear description of what you're trying to do, what you expected, and what actually happened. Include the domain, the service you're querying, and the exact error message if one was returned.