Design review catch-up
A product manager missed the review and asks what is still open on the Checkout file. Memtro lists the four unresolved threads, who raised each, the frame each is pinned to, and the replies so far.
Who said what on a Figma file, which version, and what is resolved.
Connect Figma with a personal access token and Memtro lists a team's projects and files, reads a file's pages, version history and comment threads with who said what and whether each is resolved, and the components and styles it publishes. It never fetches the design itself, and there is no sync. When you ask, and once an administrator has granted each action by name, it can post comments or reply in a thread as you, notifying the file's followers, react to comments, and manage Dev Mode links on layers. Deleting a comment you wrote is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Figma tool, reads what it needs, and answers with the source cited.
These tools change something in Figma. 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 Figma for you. Each event can start a job, with the event as its input. Figma sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Figma 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 comments on the Checkout redesign file are still unresolved, and who left them?
What changed in the Design system file this week, and who saved the versions?
Which files in the Mobile app project were modified since Monday?
List the colour styles the Design system publishes
Reply to Ana's comment on the Onboarding file that the copy is approved
A product manager missed the review and asks what is still open on the Checkout file. Memtro lists the four unresolved threads, who raised each, the frame each is pinned to, and the replies so far.
Ana Silva asked on the Onboarding file whether the welcome copy is final. Tom Baker, the copywriter, asks Memtro to reply that it is approved. Memtro posts the reply in Ana's thread as Tom, everyone on the file can see it, and the thread's followers are notified.
The teams that lean on Figma most, a question each of them asks, and what they connect beside it.
A record in Figma 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.
In Figma open the account menu → Settings → Security → Personal access tokens → Generate new token, choose an expiry and tick current_user:read, file_content:read, projects:read, file_comments:read, file_versions:read and library_content:read
For the actions add file_comments:write for comments and reactions, and file_dev_resources:read and file_dev_resources:write for Dev Mode links. Copy the token: it is shown once and expires on the date you chose
In Memtro open Connections → Figma, paste the Personal access token, optionally with the Team id from your team's URL (figma.com/files/team/<team_id>/…), and connect
Ask which comments on a file are still open
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Figma tools are the same everywhere.
Only when you ask, and only what it has been granted: post a comment on a file, or reply to an existing comment; delete a comment you wrote; add or remove your emoji reaction on a comment; attach, rename, repoint or remove a Dev Mode link on a layer. 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. In Figma open the account menu → Settings → Security → Personal access tokens → Generate new token, choose an expiry and tick current_user:read, file_content:read, projects:read, file_comments:read, file_versions:read and library_content:read.
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 Figma 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