Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Record a real browser page and cut it into a publishable vertical video. Local, no cloud.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"screenrec-agent": {
"command": "npx",
"args": [
"-y",
"screenrec-agent"
]
}
}
}Run this in your terminal
claude mcp add screenrec-agent -- npx -y screenrec-agentPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"screenrec-agent": {
"command": "npx",
"args": [
"-y",
"screenrec-agent"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"screenrec-agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"screenrec-agent"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Robert0303-C, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.5) reached the registry 7 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Let your AI agent record a real browser page and cut it into a publishable vertical video.
By xukunAI · an MCP server for Claude Code, Cursor, Codex and Hermes. Your agent records a page over CDP (no browser extension, no permission dialog), then composes the clip: device frame, held-frame callouts, punch-ins, captions, music with real ducking, end card.
Everything runs locally. No upload, no API key, no cloud render.
split puts a second recording next to the first — stacked in 9:16, side by side in 16:9, with ratio and gap to tune it. The direction follows the canvas, so the agent never has to choose. Captions, callouts, end card and music still apply in the same call.
{ "target": "vertical",
"split": { "source": "C:/rec/second.webm", "ratio": 0.5, "gap": 6 }, "captions": [{ "start": 0.8, "end": 5.0, "text": "before / after" }] }
Full guides: [English](docs/USAGE.md) · [中文](docs/USAGE.zh.md)
录制 → 设备框 → 冻结圈注 → 局部放大 → 字幕 → 结尾卡 → 成片
Every "AI video" tool generates pixels and hopes the text survives. This one doesn't generate anything: it records your actual UI and draws text with a font engine. Every digit is your real number.
The agent-facing part is the point: an agent can produce a finished clip as a tool call, not a chat suggestion.
| Tool | What it does |
|---|---|
recorder_status | recording state, bytes, bridge status |
recorder_start | start recording a tab (Chrome requires one human click — see below) |
recorder_stop | stop and save to Downloads |
recorder_files | list recent recordings |
compose_clip | the actual product: record → finished video |
compose_clip takes captions, annotations (held-frame callouts), focus (punch-ins), end_title, music, frame (phone/browser), pip (picture-in-picture), split (second recording on the same canvas).
npx (recommended) — works in Claude Code, Cursor, Codex, Hermes and any MCP client:
{
"mcpServers": { "screen-recorder": { "command": "npx", "args": ["-y", "screenrec-agent"] } } }
Then verify the install:
npx -y screenrec-agent --selftest
First run downloads the agent (~33 MB) and a pinned ffmpeg build (~201 MB) into %LOCALAPPDATA%\screenrec-agent\bin. The cache is reused afterwards, and upgrading the launcher re-downloads only the agent — ffmpeg is not fetched again. Downloads resume and retry on a dropped connection instead of failing silently.
Or use the exe directly. Download screenrec-agent.exe from the latest release, put ffmpeg.exe beside it (only compose_clip needs ffmpeg), and point command at the exe.
Published in the official MCP Registry as io.github.Robert0303-C/screenrec-agent.
| Free | Full — $39 once | |
|---|---|---|
recorder_* — record with your agent | unlimited, forever | unlimited |
compose_clip — turn a recording into a finished clip | 24 hours / 5 clips | unlimited |
| Runs locally, nothing uploaded | yes | yes |
The trial starts on your first successful compose, not on install. When it ends, compose_clip returns license_required with a purchase link — recording keeps working, nothing is deleted, nothing crashes. Check what is left with screenrec-agent --status, unlock with screenrec-agent --activate .
The only network call is activation itself. Trial state lives on your machine (three copies, clock rollback detection) because the alternative is a server that watches you use it. Deleting all three copies is equivalent to a fresh install — offline software cannot prevent that, and we would rather be honest about it than ship surveillance.
Buy: https://www.creem.io/product/prod_57FG0V8N2N4z3PrCzK0Klr · xukun.online
chrome.tabCapture needs activeTab, and activeTab only comes from invoking the extension on that tab. No script can fake it (verified: even a trusted CDP click inside an extension page fails). So:
Commercial. Source available for review; redistribution of the packaged binary is not permitted.