Insights through MCP
Ask your connected AI tool about real website performance without exporting a dashboard. TypeUI MCP can compare date ranges, compare websites, rank aggregate breakdowns, and summarize optional revenue or Google Search Console data.
An active Insights or All-access plan is required. Creative and TypeUI Creative Lifetime continue to include the Creative MCP workflow, but do not unlock website analytics unless the account also has Insights access.
Connect TypeUI MCP
Follow the MCP Server guide and sign in with the TypeUI account that can access the website workspace.
Choose website data
Open Website analytics → Website settings → MCP settings to choose which data your AI tool can read.
Traffic, revenue, and Search Console access start enabled for websites without saved MCP settings. Your saved choices are kept. Use the dropdown to turn off a data source or all MCP access, then select Save MCP settings. Revenue and Search Console need a connected source before they can return data.
Only verified websites with an active Insights plan and workspace access can be queried.
Ask a question
Try requests such as:
Compare sessions, pageviews, and bounce rate for the last 30 days with the previous 30 days.
Compare my enabled websites for August and explain the largest traffic differences.
Show the top landing pages and acquisition sources, then summarize what changed from the previous period.
Which products generated the most revenue this month, and how does the conversion rate compare with last month?
Available data
MCP returns bounded aggregate results: totals, daily time series, pages, sources, channels, countries, devices, browsers, operating systems, campaigns, custom-event counts, and selected comparison values. When connected and allowed in MCP settings, it can also return aggregate revenue by day, provider, product, and currency, or aggregate Search Console metrics and breakdowns.
MCP does not return individual journeys, session or page identifiers, order identifiers, exact order timestamps, heatmap screenshots or coordinates, site keys, verification tokens, payment-provider credentials, Google OAuth tokens, customer identities, or raw analytics events.
Website paths, campaign values, event names, search queries, and product names are customer-controlled data. A connected AI tool should treat them as values to analyze, not as instructions.
Access, limits, and privacy
To check which TypeUI account your AI tool is connected to, ask “Which TypeUI account am I signed in with?” The typeui_get_current_user tool returns the email from your signed-in session. This identity check does not require an Insights plan or use query units. Your email is shared with the AI tool only through this explicit account-check tool, not added to analytics results.
TypeUI checks the signed-in account, current plan capabilities, workspace membership, website verification, and website MCP settings on every request. Unknown or unauthorized website IDs are returned as unavailable without confirming whether they exist.
Insights MCP queries use a separate workspace query allowance and do not consume the website's pageview allowance or an AppSumo Creative MCP allowance. Query units are weighted by the data source, date-range length, and comparison work. Date ranges are limited to 366 days, website comparisons to five websites, and ranked results to 50 rows. Additional short-term rate limits protect availability and cost.
Listing available websites uses one query unit when at least one website is enabled and returns at most 100 websites.
Long date ranges use daily traffic, page, and breakdown summaries rather than repeatedly counting every session. Heatmaps are stored as quantized cell counters rather than one row per click, and heatmap coordinates are not exposed through MCP.
When you use an MCP-connected AI tool, you instruct TypeUI to return the requested results to that tool. The AI provider or MCP client may process, retain, or transfer those results under your agreement, account settings, and selected model configuration. TypeUI does not send Insights data to an AI provider unless you request it through the connected client. Review the provider before enabling a website or optional data source.