One server, several front doors
DuckDive publishes one MCP server, at https://api.duckdive.ai/mcp. Every assistant below connects to that same address. What differs is where each app hides the "add a connector" screen, which words it uses for sign-in, and which small errors people hit on the way. That is the whole reason there is one page per assistant instead of one generic page.
Pick your path
If you work in a chat app, Claude and ChatGPT are the two walkthroughs written for you, and they differ more than you might expect. If you live in a code editor or terminal, Cursor and Claude Code each add the server in a different place and suit different jobs once connected. If your tool is something else, the any-client page lists what a client must support so you can test it before you invest an hour.
The quickest route is the self-setup page. You paste one line into an assistant that already supports remote servers, and it registers DuckDive or hands you the link to approve.
How to tell the connection works
Do not trust a green tick. Ask the assistant to list your websites. If it names them, the server is reachable and your sign-in held. Then ask for a single number you can check in Google Analytics yourself, such as last week's sessions for one site. Agreement means you can move on. A mismatch often means the import has not finished or the date windows differ, so check both before suspecting the connection.
After you connect
Connecting is the cheap part. What matters is the habit that follows: asking narrow questions, naming the site and the date window, and asking the agent to show which tool it called. The verification guide and the safety guide cover that habit. If you are building your own tool rather than using an assistant, the developer page describes the server from the integrator's side.
When a connector refuses to appear
Common causes are an app plan or workspace that does not allow custom connectors, a sign-in window closed before it finished, and a stale failed attempt. The assistant pages cover the symptoms specific to each app. If your app is not listed, the any-client page sets out what a client has to support.
Check your plan before you start
Custom connectors are a feature that app vendors gate in different ways. Some apps limit them to certain plans, some require a workspace administrator to approve a server, and some expose the option only in developer settings. Before following any walkthrough, look in your app's own settings for the place connectors live, and confirm that your account is allowed to add one. The vendor's help page is the authority here, so each assistant page links to it with the month it was checked.
What the assistant can and cannot do
Through DuckDive, the assistant reads marketing data you have linked. Reading is the default posture: the tools for reporting return numbers, and the setup tools that add websites or link sources are separate and depend on the permissions of your account. The safety guide walks through exactly what is granted at each step, which is worth reading before you connect an account that belongs to a client.
Which assistant suits which work
Pick by where your questions arise. In a chat window, a long conversation lets you ask follow-ups and draft the message to a client in the same place. In an editor, the agent can look at the page you are editing while it reads the conversion data for that page. In a terminal, a script can ask the same question every Monday. The assistant pages describe a worked example for each of these situations, using fictional businesses and invented figures inside tagged blocks, so you can judge the fit before you set anything up.
