Back to blog

GrainQL 6.5: Multi-Site MCP, Reports, and Channels

GrainQL 6.5 connects your AI tools to every site on your account, turns a typed sentence into a report, and shows every campaign touch before a sale.

GrainQL Team

GrainQL6 min read
GrainQL 6.5 release cover

GrainQL 6.5 is out today, and we are really happy with this one.

It has three big pieces. A new MCP that can see every site on your account. A Reports page where you type a question and get a chart. And Channels, which shows the full path a buyer took across your campaigns before they paid you.

All three came from the same place: things you kept asking us for. Here is what each one does and why we built it.

The new MCP: one connection, every site#

If you have not used it yet, the GrainQL MCP lets you talk to your analytics from the AI tools you already work in, like Claude or Cursor. You ask a question in plain words and it runs the query on your GrainQL data.

The first version had two problems. We heard about both of them a lot.

It only knew one site. Each connection was tied to a single workspace. If you ran three stores, or managed sites for clients, you needed three connections and you could never ask about them together.

It kept logging you out. Sessions expired at bad moments, and you had to approve the connection again in the middle of your work.

6.5 fixes both.

When you connect now, you choose how far the connection reaches: your whole account, or just one workspace. With an account-wide connection you can ask things like "how did signups do across my sites this week?" and get one answer that covers all of them. If you would rather keep a connection limited to a single client's site, that still works.

Sign-in is steadier too. Sessions renew quietly in the background, so the connection you set up on Monday is still there on Friday.

You stay in control the whole time. Every connection is listed under Settings, with the last time it was used. Revoke one and it stops working.

Reports: type the question, get the chart#

Most report builders start with an empty canvas and a lot of dropdowns. You have to know what you want, and then you have to know where the tool hides it.

Reports starts with a sentence.

Type something like purchases by country weekly. GrainQL completes the sentence as you go, the way your phone keyboard does, and draws the report when you press Enter. You can write it the way you would say it out loud, in your own language. If you would rather click than type, the builder on the side does the same job.

A few things we care about here:

  • Suggestions come from your own data. GrainQL looks at the events your site really tracks and offers the reports worth running. If you sell with coupon codes, it will suggest a breakdown by coupon. It will not suggest a report you cannot run.
  • You pick the view. Lines, columns, donuts, heatmaps, or a plain table. Hover any point and the big number at the top changes to that exact value.
  • You can break it down twice. Country and device. Campaign and landing page. Two dimensions at once, by hour, day, week, or month.
  • It leaves the building. Export to CSV, XLSX, JSON, or PNG. Every report is also a link, so sharing one with a teammate is a paste.

Kai sits next to the report the whole time. When a number looks odd, ask why, and Kai already knows which report you are looking at.

Write your first report

Reports is live in every GrainQL account. Open it, type a question, and see what comes back.

Open Reports

Channels: every touch before the sale#

Here is a story you may know. You run an Instagram campaign. Your analytics says it converted almost nobody. You turn it off. Two weeks later, sales are down and you cannot tell why.

What happened is that Instagram was doing the introductions. People saw the ad, left, came back from your newsletter a few days later, then searched your name and bought. Your report gave all the credit to the last click, and the campaign that started everything looked like a waste.

Channels shows the whole path.

For every buyer, GrainQL keeps the campaign touches that led to the purchase, up to 10 of them over 90 days. Channels lays them out as a flow, from first arrival to purchase, so you can see:

  • Which campaigns open the door and which ones close the sale.
  • Which combinations convert best. An ad followed by an email can behave very differently from the ad alone.
  • Where people give up. The paths with lots of intent and few purchases are the ones worth fixing first.

It also works without cookies, like the rest of GrainQL. There is no cross-site tracking and no new banner to add to your site.

One honest note. Channels can only record full journeys from the day the new tag reached your site. For the time before that, GrainQL estimates shorter paths from the first-touch and campaign data it already had. Estimates are labeled as estimates, and you can switch them off if you only want measured journeys.

How to get 6.5#

You already have it. Reports and Channels are in your sidebar, and the new MCP is ready to connect from Settings.

If you use the GrainQL Tag snippet, the journey tracking behind Channels arrives on its own. There is nothing to install and nothing to migrate.

New to GrainQL?

Paste one tag and ask your first question today. 14 days free, no card.

Start free trial

What comes next#

We are going to keep pulling these three closer together. Reports you can build by asking Kai. Channels paths you can open as a report. An MCP that can reach more of what GrainQL knows.

If you try 6.5 and something feels off, or something is missing, tell us. A lot of this release started as a message from one of you.

Related articles