A privacy check
Priya Sharma, marketing manager at Acme Ltd, asked which videos in the account were public. Memtro listed them with plays, folder and upload date, and flagged an internal training video among them.
Which of our videos are public, and how many plays have they had?
Vimeo connects Memtro to your video hosting. It reads the account's videos with title, privacy, plays, tags, folder and dates, one video's details and comments, folders and the videos in one, showcases, and the storage quota. When asked, and once an administrator has granted the action by name, it can comment on a video, rename or re-describe it, change who can watch, comment on or embed it, add or remove tags, manage folders, delete a comment and delete a video. Video passwords, unlisted links, embed codes and download links are never passed on.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Vimeo tool, reads what it needs, and answers with the source cited.
These tools change something in Vimeo. 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 Vimeo 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 of our videos are public?
What were our most played videos this year?
What comments are on the product launch video?
How much storage do we have left?
Make the onboarding walkthrough unlisted
Priya Sharma, marketing manager at Acme Ltd, asked which videos in the account were public. Memtro listed them with plays, folder and upload date, and flagged an internal training video among them.
Tom Reilly, content lead at Northwind, asked Memtro to stop anyone outside the team watching last year's pricing video. Memtro set its privacy to team in Vimeo, so only team members can watch it. Nobody was notified.
The teams that lean on Vimeo most, a question each of them asks, and what they connect beside it.
A record in Vimeo 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.
On developer.vimeo.com, open My Apps, create an app or open yours, and choose Generate Access Token with Authenticated (you).
Tick public and private to read, and edit, interact, create or delete only for what Memtro may change. Generate, and copy the token from Personal Access Tokens. It acts as the user who made it.
In Memtro, open Connections → Vimeo and paste it into Personal access token.
Ask your first question: which of our videos are public?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Vimeo tools are the same everywhere.
Only when you ask, and only what it has been granted: comment on a video (the owner may be notified); rename a video or change its description; change who can watch, comment on, embed or download a video; add a tag to a video; remove a tag from a video; create a folder; add a video to a folder; remove a video from a folder (the video is kept); delete a comment the user wrote; delete a video (kept in Recently Deleted for 30 days). 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.
Personal access token. On developer.vimeo.com, open My Apps, create an app or open yours, and choose Generate Access Token with Authenticated (you).
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