The short answer
Sign in to claude.ai, open the connector link DuckDive has already filled in, press Add and then Connect, and finish on your Google login. Until you select Connect, Claude reports no tools available. After that, Claude reads GA4, Search Console, Google Ads and Local Services Ads for each of your sites, and carries the site and the week from one question into the next.
- Select Connect straight after Add, or every new chat will say it has no DuckDive tools.
- Words like "that week" or "the same for my other site" reuse what Claude already found, so it only fetches what is new.
- Add the connector on the web or desktop first; the Claude phone app picks it up when you sign in there.
Add Google Analytics to Claude through one DuckDive link
A custom connector in Claude normally means typing a name and a server address into a form. DuckDive publishes a link that fills the form in. Sign in to claude.ai, then open it.
https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=DuckDive&connectorUrl=https%3A%2F%2Fapi.duckdive.ai%2Fmcp
Open Claude with DuckDive filled in
-
Check the form Claude opens
The name reads DuckDive and the URL reads
https://api.duckdive.ai/mcp. Leave any setting marked Detected alone, as Anthropic's connector docs advise (as of November 2026). If the dialog shows Continue, select it. -
Select Add
DuckDive now sits in your connector list, registered but not yet signed in.
-
Select Connect next to DuckDive
Do it right away. A DuckDive page opens in a new tab and asks you to continue with Google.
-
Continue with Google
First-timers get a DuckDive account out of that single click; there is nothing to fill in. Returning users land on a permission page instead, and its one checkbox, Also allow actions, decides what a Claude chat can do later. Ticked, Claude may register a new website and attach its Google properties when you ask. Cleared, this connection only ever reads. Make the choice, then press Allow.
-
Open a new chat and ask
Start a fresh conversation. If DuckDive is off, select the + button, open Connectors and switch it on.
Prefer the menus? Go to Customize, then Connectors, then Add custom connector, and paste the same address. Anthropic renames menus now and then; whatever the label says, you want the screen that lists connectors. There is no API key: Claude signs in with OAuth and holds a DuckDive access token, never your password.
On Team or Enterprise
Per Claude's help center (as of November 2026), an Owner adds DuckDive under Organization settings, then Connectors. Members find it under Customize with a Custom label and select Connect. Adding it for the organization shares no DuckDive login: every member authorises their own, and their Claude is limited to the websites on that member's DuckDive seat.
The "no tools available" moment and how to get past it
This is where first attempts stall. After Add, Claude knows where DuckDive lives but has no permission to use it. DuckDive's server refuses unsigned requests, so Claude gets no tool list and reports no tools available. Nothing is broken; the sign-in has not happened yet.
Selecting Connect starts that sign-in. When you come back from the DuckDive tab, the tools fill in. As of November 16, 2026 the DuckDive server exposes 22 of them: four to find your websites, three that report setup and import status, four actions, and eleven that read GA4, Search Console, Google Ads, Local Services Ads, Yext and Local Falcon.
- DuckDive shows Connect, or says no tools available. Select Connect and finish the DuckDive page.
- Claude shows Reconnect instead. Select Reconnect and sign in again.
- You left the DuckDive tab open over lunch. That sign-in tab stays valid for only 30 minutes, per DuckDive's agent guide. Start again from Connect in Claude rather than refreshing the old tab.
- The DuckDive page loops. Log in at analytics.duckdive.ai in the same browser, close the looping tab, and press Connect in Claude once more.
To prove it works, ask something only DuckDive can answer. If Claude says it has no such tools, the chat toggle is off; see the troubleshooting list below.
Ask your agentBefore anything else: how many DuckDive tools were you handed in this conversation, and which of my websites already have Google Analytics attached?
Tools it calls list_websites
An empty list means DuckDive holds no websites yet. Ask Claude to add one, as the second worked example shows, or read the walkthrough of agent-run setup.
Follow-up questions, and the tools Claude calls for each
The reason to ask Claude instead of opening a report is the second question. Something in the answer looks odd, so you ask about the odd thing. Claude keeps earlier turns in view, so you never restate the site, metric or period. It only calls DuckDive for numbers it has not fetched yet.
Two constraints sit under every follow-up. A data call targets a single website, so when you say "all my sites" Claude quietly loops through them. And no call accepts a start date: each takes one of six named periods counted back from today, ranging from a week to a year. Any "that week" you mention, Claude has to rebuild out of those periods, which is what the definitions below spell out.
- Best week
- Claude's own grouping.
get_ga4_overviewreturns sessions and conversions per day, so Claude adds the days into 7-day blocks and picks the top block. - Week before last
- The 14-day window minus the 7-day window. Channel and landing page tools return totals for a whole window, so this is the only past week Claude can split by source or page.
- Ordinary week
- The 90-day total divided by 90/7, about 12.9 weeks. It includes the best week, so it flatters the baseline slightly.
| You type | Claude reuses | Claude calls |
|---|---|---|
| Where was the strongest seven-day run? | Nothing yet | list_websites, then get_ga4_overview per site |
| What was different about that week? | The winning site and which week won | get_ga4_channels plus get_ga4_landing_pages over the 7, 14 and 90 day periods |
| Did it last? | The page that stood out | get_ga4_landing_pages, last 7 days |
| Same for my other site, search clicks only | The method and the site list | get_search_console_summary, then get_search_console_pages |
Call pattern worked out from the inputs and outputs each DuckDive tool declares, November 16, 2026.
Save the opening question. It works on any account with GA4 linked, whether you run two sites or twenty.
Ask your agentAcross my sites, where was the strongest seven-day run of conversions in the past 90 days?
Tools it calls list_websites get_ga4_overview
Worked example: from 'best week' to 'why that week' in three turns
A fictional freelance marketer looks after two client sites in DuckDive: Ravensford Climbing Gym and Ostlund Design Studio. Every turn below only reads data.
Turn 1
Across my sites, where was the strongest seven-day run of conversions in the past 90 days?
list_websitesreturns Ravensford and Ostlund, each carrying GA4 plus Search Consoleget_ga4_overviewRavensford Climbing Gym, daily sessions and conversions for 90 daysget_ga4_overviewOstlund Design Studio, same window
Ravensford Climbing Gym, by a wide margin. I added each site's daily conversions into 7-day blocks, counting back from the latest day in the data, and dropped the leftover 6 days. Conv. is conversions in that best week; Usual is the ordinary-week figure defined above.
| Site | Best week | Conv. | Usual |
|---|---|---|---|
| Ravensford Climbing Gym | 8 to 14 days ago | 61 | 34 |
| Ostlund Design Studio | 36 to 42 days ago | 9 | 6 |
Ravensford's best week also had 2,140 sessions against an ordinary 1,520, so the conversion rate rose too, from 2.2% to 2.9%.
Turn 2
What was different about that week? Compare its traffic sources and top landing pages with an ordinary week for the same site.
get_ga4_channelsRavensford by traffic source, last 14 days and last 7 days; the difference is the best weekget_ga4_channelslast 90 days, divided down to an ordinary weekget_ga4_landing_pagesthe same three windows, top pages with conversions
Instagram and your newsletter, and most of the extra traffic landed on one page. Visits from Google barely moved. First, sessions by source in the best week against a usual week, with the best week's conversions. Then the best week's top landing pages, with what each converts in a usual week:
| Source | Best | Usual | Conv. |
|---|---|---|---|
| 780 | 720 | 14 | |
| instagram.com | 520 | 140 | 24 |
| (direct) | 410 | 390 | 9 |
| newsletter | 230 | 120 | 11 |
| Other | 200 | 150 | 3 |
| Page | Sessions | Conv. | Usual |
|---|---|---|---|
| /youth- | 640 | 29 | 3 |
| / | 520 | 10 | 11 |
| /day-pass | 380 | 12 | 12 |
Instagram sent about 3.7 times its usual sessions and the newsletter nearly twice. The youth climbing camp page took 640 sessions against a usual 90 and produced 29 of the week's 61 conversions. That reads like a promoted camp launch, not a search win. (I can only subtract pages that sit in both top 100 lists; all three here do.)
Turn 3
Did the camp page keep converting after that week, or did it drop back?
get_ga4_landing_pagesRavensford, last 7 days; no need to look the site up again
It cooled off but stayed well above normal: 210 sessions and 6 conversions in the last 7 days, against 640 and 29 the week before and an ordinary week's 90 and 3.
Look at the call counts: a lookup plus one call per site, then six calls with no lookup, then one. Each follow-up cost less because Claude kept the site and the week.
The example is kind in one way: the best week was the week before last, the only past week Claude can split by source. Switching Ostlund to Search Console changes the arithmetic. get_search_console_summary returns weekly points, each starting on a Monday, not days, so Claude reads the top week straight off the 90-day series instead of adding days up. Those calendar weeks will not line up exactly with the last-7 and last-14-day windows that get_search_console_pages accepts, so a fair answer names the Monday the best week began and says plainly that a page breakdown exists only for the two most recent 7-day windows.
Ask your agentNow do the same for Ostlund Design Studio, but only for Search Console clicks.
Tools it calls get_search_console_summary get_search_console_pages
"The same" here means the whole method: find the best week, then explain it. Claude swaps the GA4 tools for their Search Console counterparts and already has Ostlund's website ID from the list it pulled in turn one.
Run those three turns on your own sites
Connect Claude, ask which site had its best week, and keep pulling the thread until the answer is a decision.
Free for 2 sites · No credit card
Asking from the Claude mobile app
Plenty of marketing questions arrive away from a desk: a client texts, a meeting starts in five minutes. The Claude app on iOS and Android answers them from the same DuckDive connection.
Set it up on a computer first. Anthropic's help article on connectors says a connector you add in Claude on the web or desktop is available in the phone app the next time you log in there, and that installing connectors from mobile is in beta (as of November 2026). DuckDive's connector guide agrees: once added, it works in the desktop and mobile apps, with the same account and sites.
On a small screen, ask for short lists, not wide tables, and name the site up front.
Ask your agentPhone check, two lines max: did Ravensford get more conversions in the last 7 days than in the 7 before, and which traffic source moved most?
Tools it calls get_ga4_overview get_ga4_channels
That prompt fits the fixed windows exactly. Ask for "since Tuesday" and Claude has to approximate, and should say so.
Worked example: Claude adds a second website for you
The same freelancer takes on a candle shop. Its owner has given the freelancer's Google account access to the shop's GA4 property and Search Console site. The freelancer holds a DuckDive admin seat with Also allow actions ticked, and has left Claude to ask before each use of DuckDive's setup tools. Halfway through, the freelancer turns one of those requests down, to see what it would have touched.
Turn 1
Set Tallowbrook Candles up in DuckDive, with the shop's analytics and search data attached.
add_websiteapproval request shown and approved; adds tallowbrookcandles.example, next step: choose_sourceslist_available_sourcesa read, so no request; one GA4 property and one Search Console domain property sit in ready_to_linkconnect_website_sourcesapproval request shown and declined; nothing runs
Understood, nothing is linked. Tallowbrook Candles is in DuckDive with no data sources, so no history is importing. Here is what the declined call would have linked:
| Candidate | Why | Included |
|---|---|---|
| GA4: Tallowbrook Candles | Matches the domain | Yes |
| sc-domain: | Domain property | Yes |
| GA4: Tallowbrook Wholesale | Another domain | No |
Say go and I will send the same call again, or tell me what to change.
Turn 2
Go ahead with those two.
connect_website_sourcesapproval request shown again and approved; next step: importingget_sync_statuseach new source reports its import as under way
Linked. The shop's GA4 and Search Console history are on their way in; give it a few minutes before trusting the totals.
Turning a request down is cheap, because a declined call never ran. Here it left a website with no sources, and DuckDive imports nothing for a website until a source is linked, so there was nothing to clean up. The prompt also named the site, which is why Claude never asked which one you meant.
A decline covers one call in one chat; the Blocked setting in the next section covers every chat. When a setup tool is unavailable or refused, DuckDive's agent guide tells the assistant to send you to the setup page in your browser, so expect a link from Claude rather than repeated attempts.
Once the import is ready, the shop joins the earlier conversation.
Ask your agentHas Tallowbrook's import finished? If it has, add Tallowbrook to the best-week comparison from earlier in this chat.
Tools it calls get_sync_status get_ga4_overview
Taking on twenty clients in a week is a different job from one candle shop, and it has its own walkthrough: bringing a large roster into DuckDive by agent.
Allowing actions, or keeping Claude read-only
What Claude may change comes down to two switches, one in each product. On DuckDive's side, the Also allow actions box, which only counts for an Agency Admin or Client Admin seat. On Claude's side, per-tool permissions in Customize, then Connectors, where a tool can ask each time or be Blocked. Anthropic advises Always allow only for servers you trust (as of November 2026).
Of the 22 tools Claude sees, just four write anything: add_website, connect_website_sources, refresh_website_data and create_scheduled_report. Ticking the box never widens that set. No tool erases stored history, alters your Google sign-in, or mails a report to an inbox other than yours.
| Setup | Suits | What Claude can do |
|---|---|---|
| Actions unticked in DuckDive | People who only ask questions | Read only; setup happens in your browser |
| Actions ticked, approval each time | Admins adding a site now and then | Changes after you approve each call |
| Actions ticked, action tools Blocked in Claude | Admins who want setup off in daily chats | Read only until you unblock the tools |
| Always allow on action tools | One long session adding many sites | Changes without stopping; switch back afterwards |
| Team member seat | Analysts and account managers | No changes, whatever the boxes say |
Permission rules taken from Anthropic's documentation on unlisted connectors and DuckDive's AI connector guide on November 16, 2026.
You can also state the rule at the top of a chat; the switches enforce it either way.
Ask your agentFor this chat, read from DuckDive only. If a site or a data source is missing, tell me what you would add and stop there.
Tools it calls list_websites list_available_sources
For wider risks, such as instructions hidden inside page titles or search queries, read whether it is safe to connect AI to Google Analytics.
If Claude cannot see DuckDive
These fixes live inside Claude. Work down the list in order.
Claude-side checks, in order
- Added but never connected. Open Customize, then Connectors, and select Connect next to DuckDive.
- Reconnect is showing. Select it and finish the DuckDive page within 30 minutes.
- Off in this chat. Select the + button, open Connectors, switch DuckDive on, or start a new chat.
- Free plan, slot already taken. Claude Free allows one custom connector, so remove the other one or move to a paid Claude plan.
- Workspace member without Owner rights. Ask an Owner to add DuckDive for the organization, then select Connect yourself.
- Typed the address by hand. It must be exactly
https://api.duckdive.ai/mcp. Claude does not let you change sign-in settings after adding, so remove the connector and add it again. - Claude says it is not allowed to add a site. Your connection is read-only or your seat is not an admin. Disconnect DuckDive in Claude's connector settings and connect again with Also allow actions ticked, or ask your DuckDive admin.
If the tools are there but the answers look wrong, such as empty numbers or a source that seems stale, the cause is not specific to Claude. The remote MCP server page for any client has the symptom-by-symptom list.
Plans, team workspaces and privacy in Claude
Which Claude plan you need
DuckDive's connector guide says it works on any Claude plan. Anthropic offers custom connectors by URL on Free, Pro, Max, Ultra, Team and Enterprise, with Free limited to one (as of November 2026).
DuckDive is free for one website with no credit card; paid plans are per site, shown below, and billed separately from Claude.
Who sees what
- Claude reaches DuckDive from Anthropic's cloud, not from your laptop or phone, according to Anthropic's help center (as of November 2026).
- Your chat transcript never reaches DuckDive. What it keeps is a short audit trail per call: the tool name, the website it targeted, a timestamp, success or failure, and a copy of the request with secrets scrubbed out.
- What Anthropic does with numbers returned into a chat falls under Anthropic's own policies.
- Revoking works from either end: delete DuckDive from Claude's connector list, or press disconnect on DuckDive's AI Connectors page, and the access stops immediately.
When Claude and DuckDive are the wrong pair
This setup is built for asking and following up across a handful of sites or a few dozen. Skip it in these cases.
- You need exact dates. Last year's promotion week is out of reach: windows are fixed and the longest is 12 months.
- You need finer detail. GA4 device, country, events and revenue are not exposed, nor are Ads campaigns or review text.
- You have one GA4 property and want all of GA4. Google's Analytics MCP server documents Claude Desktop and Claude Code, and adds realtime and funnel reports, but runs locally and needs Python 3.10 or higher plus a Google Cloud project (as of November 2026). See our comparison with Google's server.
- You live in a code editor. Claude Code suits work that ends in a file.
- Your team works in ChatGPT. Connecting ChatGPT comes with a different plan requirement, explained on its own page.
- You want numbers without asking. For a recurring brief, see giving your AI chief of staff marketing data.
Beyond the four Google sources, Claude can also see Yext listing status with review counts, and Local Falcon map ranks, through DuckDive, and that is the full set. Questions about your CRM pipeline or call recordings need a second connector beside this one.
What Claude users ask before connecting
Why does Claude say no tools are available after I added DuckDive?
Adding the connector only registers it. DuckDive shares its tools once you sign in, so select Connect next to DuckDive in Claude's connectors and continue with Google on the page that opens. If Claude offers Reconnect, select that instead.
Does it work on the free Claude plan?
Yes. Claude Free allows one custom connector, so DuckDive can be that one. If another service already holds the slot, remove it or upgrade Claude. DuckDive itself is free for one website.
Can I ask from the Claude app on my phone?
Yes. Add DuckDive in Claude on the web or desktop first. Anthropic says connectors added there appear in the iOS and Android apps the next time you log in, with the same sites.
Does Claude remember my sites in a new chat?
A new chat starts without the earlier turns, but the connection stays. Name the site in your first question, or ask Claude to list your websites, and it picks up from there in one call.
Can Claude compare a specific week from last year?
No. Every DuckDive data call is anchored to today, and the furthest back any of them reaches is twelve months, so a week from last spring or last year's sale has nothing Claude can request. Inside the past 90 days it can still isolate a single week by summing daily figures, the way the worked example does.
Can Claude change my Google Analytics or Ads accounts?
No. Whatever Claude pulls from Google through DuckDive, it pulls as a read. The only writes available happen inside your DuckDive account (registering a website, attaching sources, re-importing recent days, scheduling an emailed report that lands in your own inbox), and Claude gets them only on an admin login that ticked Also allow actions. Removing stored history and unhooking your Google login are outside its reach entirely.
Sources
- Anthropic: Add a connector that isn't in the directory. Backs the plan list, the one-connector Free limit and the Detected settings advice. Opened November 16, 2026.
- Anthropic support: Get started with custom connectors using remote MCP. Backs the Owner steps for Team and Enterprise and the point that Claude connects from Anthropic's cloud. Opened November 16, 2026.
- DuckDive: Set up DuckDive with your AI assistant (agents.md). Backs the 30-minute sign-in limit and the setup-page fallback. Opened November 16, 2026.
- Anthropic support: Use connectors to extend Claude's capabilities. Backs the phone-app behaviour and the mobile beta note. Opened November 16, 2026.
- DuckDive: DuckDive for Claude, ChatGPT and other AI apps. Backs the action limits, the call log and the any-plan statement. Opened November 16, 2026.
- Google: Try the Google Analytics MCP server. Backs the Python, Google Cloud and client details in the wrong-fit list. Opened November 16, 2026.
Last reviewed . Claude and Anthropic are named to describe compatibility only; this page is not endorsed by Anthropic. Ravensford Climbing Gym, Ostlund Design Studio and Tallowbrook Candles in EXAMPLE DATA blocks are fictional.
