Is our video playback healthy, and which player errors are viewers hitting?
Mux hosts and streams your video, and Memtro reads the library and how playback is going. It reads video assets with status, duration and quality, live streams, and minutes delivered per asset. From Mux Data it reads views, metrics such as startup time and rebuffering, open incidents and top player errors. When asked and granted, it can create, update or delete assets and playback ids, manage live streams, cancel uploads and edit annotations. Mux can tell Memtro when a video is ready or a stream goes live, and a job can start on it. Stream keys are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mux tool, reads what it needs, and answers with the source cited.
These tools change something in Mux. 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 Mux for you. Each event can start a job, with the event as its input. Mux signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mux 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.
Which player errors did viewers hit most this week?
What is our median startup time over the last 7 days?
Are there any open Mux Data incidents?
Which assets delivered the most minutes yesterday?
Change the title of the launch video to Spring Launch 2026.
Priya Sharma, video product lead at Acme Ltd, asked whether playback had got worse since Tuesday's player release. Memtro read the viewer experience score and the top player errors for the week, and listed the open incidents with their affected views.
When Mux told Memtro that a new training video was ready to play, a job started at Northwind. It read the asset's duration and public playback id and posted them for Dan Fletcher, who manages the learning portal.
The teams that lean on Mux most, a question each of them asks, and what they connect beside it.
A record in Mux 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.
Jotform
DataForSEO
Moz API
Hygraph
Paperform
Kajabi
Kontent.ai
Teachable
WufooIn the Mux dashboard, an organisation admin opens Settings, then Access Tokens, and generates a token for the right environment. Tick Mux Video, Mux Data and System Write permissions, as they cannot be added later.
In Memtro, open Connections → Mux and paste the Access Token ID and the Secret Key.
An administrator grants the asset, live stream and annotation actions by name to the teams that may use them. Events are turned on from the connection's Events tab.
Ask which player errors viewers hit most this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mux tools are the same everywhere.
Only when you ask, and only what it has been granted: update a video asset's title, external id, passthrough or thumbnail time; create a video asset from a file URL (billed for encoding, storage and delivery); delete a video asset permanently; add a public or signed playback id to an asset; delete an asset's playback id; create a live stream (billed while streaming); enable a live stream; disable a live stream, ending any broadcast; signal that a live stream's broadcast is complete; delete a live stream permanently; cancel a direct upload; add a Mux Data annotation; update a Mux Data annotation; delete a Mux Data annotation. 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.
Access Token ID and Secret Key. In the Mux dashboard, an organisation admin opens Settings, then Access Tokens, and generates a token for the right environment. Tick Mux Video, Mux Data and System Write permissions, as they cannot be added later.
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 Mux 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
