DataEase AI integrations - connect your brand evidence

How do you connect your assistant through MCP?

DataEase AI MCP connects your assistant to saved brand insights, content and traffic through 23 read tools. One additional tool records a fix you already completed, with your confirmation. Growth and Business include access by default, subject to workspace access settings.

Open Account Settings → Connections → DataEase MCP in the Brand Intelligence application. Create a personal workspace token, save its one-time secret, then configure a remote Streamable HTTP connection to https://mcp.dataease.ai/mcp with an Authorization: Bearer header containing that token.

Use a client that supports custom bearer headers. OAuth-only clients are not supported. The server reads saved results and may fetch Google reports on demand; it does not create content, run agents or scans, publish, request indexing or spend AI credits. Recording a completed fix is separate from doing or verifying the work.

Set up the DataEase AI MCP connection

The guide includes token creation and revocation, example prompts, all 24 tools, pagination and troubleshooting. Starter and Pay As You Go do not include MCP by default. Check effective access in Connections and compare DataEase AI plans.

How does Google Search Console connect?

You authorise the property with Google from your brand settings, and DataEase AI reads index coverage for your audited pages across 3 trend windows: 7, 28 and 90 days. Indexing is one of the 6 signals compared as a matched pair after a fix.

Index coverage is the least glamorous of the four integrations and the one that catches the most embarrassing problems. A page that is not indexed is a page most retrieval paths never reach, and the reasons are usually boring: a stray noindex tag, a canonical pointing somewhere unhelpful, a redirect chain nobody remembers adding.

Three windows exist because indexing moves slowly. The 7 day view tells you what just happened, 28 days shows the current state of play, and 90 days is where a slow drift becomes obvious. What Search Console cannot tell you is whether an AI assistant read the page, which is the gap the Cloudflare Worker fills.

What does GA4 add?

GA4 supplies the human side. DataEase AI reads total visits and visits from AI referrers, which are 2 of the 6 tracked outcome signals. It cannot see AI crawlers, because bots such as GPTBot never run the JavaScript that GA4 depends on.

Visits from AI is the number most founders actually want. It is the count of people who arrived on your site from an AI assistant, which is the closest thing there is to a commercial receipt for AI visibility work: somebody asked a question, your name came up, and they clicked through.

Total visits sits next to it as context. On its own it is the noisiest signal on the page, because a launch or a newsletter can swamp anything a schema fix did. Read as a pair, they separate a general traffic bump from a genuine shift in how you are being discovered.

The limit is worth being blunt about. GA4 only sees browsers running JavaScript, so a site can be fetched heavily by AI crawlers and show nothing at all in GA4. That is a property of the tag, not a configuration mistake, and it is exactly why the fourth integration exists.

How does Cloudflare log AI crawler hits?

With a small Worker on the zone you already run. It reads the user agent of each request, records hits from 28 AI crawlers, then passes the request through to your origin unchanged. Setup is about 5 minutes and the Cloudflare free plan is enough.

Crawler requests never reach a browser, so they never reach a tag. They exist only in server or edge logs, which is why the capture point has to be the edge. The Worker is one script and one route, it adds nothing you would notice to response times, and it does not change what your visitors receive.

What you get back is the crawl side of the story: visits by bot over time, how often each page is re-fetched, and the coverage gaps where important pages are never fetched at all. One busy brand logged roughly 335,000 crawler visits in 30 days, which is traffic that had been completely invisible in its analytics.

The full breakdown of which bots these are and how to read the numbers is on the AI crawler analytics page. AI bot crawls is also one of the 6 signals used in outcome tracking, so this is the integration that tells you whether a page you fixed was ever re-read.

Do you need all four?

No. All 4 are optional and DataEase AI scans without any of them. They matter for outcome tracking: 4 of the 6 signals compared after a fix come from GA4, Search Console and Cloudflare rather than from the scan itself.

A sensible order exists. Connect GA4 first, because visits from AI is the signal that turns a visibility score into something a founder can talk about with a board. Add Search Console next, since index coverage is cheap to connect and catches technical problems that quietly cost you retrieval. Add the Cloudflare Worker when you want to know whether AI systems are actually reading you rather than inferring it.

MCP comes last, and if you are on Growth or Business and already building your own tooling around the data. It is a power feature, not a prerequisite.

With none of them connected you still get the core of the platform: audits, competitor benchmarking, and how ChatGPT, Perplexity and Gemini describe you. Connect them and you can also answer the harder question of whether a change you shipped moved anything, which is what proving an AI visibility fix worked is about.

What should you know before connecting your data?

Choose among 4 connections based on the question you need to answer: MCP for assistant access, Search Console for search data, GA4 for visits and Cloudflare for crawler logs. The answers below explain access, setup and what each source can measure.

What should you read next about your AI visibility data?

Start with the MCP setup guide if you want your assistant to read saved evidence. These 3 related guides explain crawler requests, outcome tracking and plan limits, helping you choose which connection supports your next brand presence decision and what to measure afterward.