Ask for the Fullstory replay of a customer's recent sessions when they report a bug.
Connect Fullstory with an API key and Memtro reads one person's most recent sessions with the replay link and start time, found by email or user id. It also reads saved segments and quota use, and with an Architect key lists identified users. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can add timeline annotations, create or update identified users and record custom events, none of which can be removed from Memtro. With an Architect key it can permanently delete a user.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fullstory tool, reads what it needs, and answers with the source cited.
These tools change something in Fullstory. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Fullstory for you. Each event can start a job, with the event as its input. Fullstory signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Fullstory 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.
Fullstory + MemtroShow me the replay of dan.fletcher@northwind.example's last session
Which saved segments did Priya create?
How much of our Fullstory session quota have we used this month?
Add an annotation for the v2.4 release at 10am today
Record a Plan Upgraded event for user id 48213
Support gets a report from Brightwave Ltd that checkout froze. Memtro finds the customer's five most recent Fullstory sessions by email, newest first, and returns the replay link for the one that started at 14:12, just before the report came in.
After the pricing page goes live, product lead Sofia Marquez asks Memtro to annotate the timeline. Memtro adds "Pricing page changed" at that moment. Everybody in the Fullstory account sees it on their charts, nobody is notified, and it cannot be removed from Memtro.
The teams that lean on Fullstory most, a question each of them asks, and what they connect beside it.
A record in Fullstory 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
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn Fullstory open Settings → Integrations → API Keys, press Create key, name it and choose its permission level, then copy it: it is shown once
Standard covers sessions, segments, quotas, annotations, identified users and custom events. Listing or deleting identified users needs an Architect key, available only on Fullstory's Enterprise plan
In Memtro open Connections → Fullstory, paste the API key and connect
Ask for Priya Sharma's sessions from yesterday
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fullstory tools are the same everywhere.
Only when you ask, and only what it has been granted: add an annotation (a labelled moment, such as a release) to the Fullstory timeline; create or update an identified user (upsert by your app's uid); update an identified user's name, email or properties; delete an identified user and their data (permanent, Architect key); record a custom event against a user or session (counts against the server event quota). 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.
API key. In Fullstory open Settings → Integrations → API Keys, press Create key, name it and choose its permission level, then copy it: it is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Fullstory for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
