Which checkout pages had the most friction this week?
Mouseflow records how visitors use your website, and Memtro turns that into answers. It reads session recordings with pages, duration, friction, device and tags, and one recording's path page by page. It reads heatmap statistics per page, funnel conversion by step, form analytics by field, and tallied feedback survey answers. When asked and granted, it can tag, star or mark recordings watched, set their variables or delete them. It can stop or start recording, create or delete journeys and tracked forms, and delete funnels. Visitor IP, city and free-text survey answers are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mouseflow tool, reads what it needs, and answers with the source cited.
These tools change something in Mouseflow. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Mouseflow is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Mouseflow + MemtroWhich pages have the most friction on the checkout this week?
Where do visitors drop out of the sign-up funnel?
Which field in the contact form do people leave blank most often?
How did visitors answer the pricing page survey?
Tag the recording I just watched as a payment bug.
Priya Sharma, e-commerce manager at Acme Ltd, asked which checkout pages had the most friction this week. Memtro read Mouseflow's heatmap statistics and named the delivery page, with its friction score, scroll reach and exits.
Dan Fletcher, UX designer at Northwind, asked Memtro to tag a session where the promo code field failed. Memtro added the tag, so the whole website team could filter for it.
The teams that lean on Mouseflow most, a question each of them asks, and what they connect beside it.
A record in Mouseflow is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
HolisticsIn Mouseflow, open Your profile, then API Keys, and create or copy a key. Note whether the endpoint shown is api-us or api-eu.
In Memtro, open Connections → Mouseflow and enter your Login email and API key. Set Region to eu if your endpoint is api-eu.
The key has your Mouseflow user's access. An administrator grants the recording and website actions by name to the teams that may use them.
Ask which pages have the most friction on the checkout this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mouseflow tools are the same everywhere.
Only when you ask, and only what it has been granted: add a tag to a session recording; remove a tag from a session recording; star or unstar a session recording; mark a session recording watched or unwatched; set or clear custom variables on a session recording; delete a session recording permanently; stop or start recording visitors on a website; create a journey (flow) around a page; delete a journey; start tracking a form on a page; delete a tracked form and its report; delete a funnel and its report. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Login email and API key, plus region. In Mouseflow, open Your profile, then API Keys, and create or copy a key. Note whether the endpoint shown is api-us or api-eu.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
