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)
Probe, trim, transcode and extract frames or audio from local video files with ffmpeg.
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": {
"videokit": {
"command": "npx",
"args": [
"-y",
"@reneturcios/videokit",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add videokit -- npx -y @reneturcios/videokit mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"videokit": {
"command": "npx",
"args": [
"-y",
"@reneturcios/videokit",
"mcp"
]
}
}
}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": {
"videokit": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/videokit",
"mcp"
]
}
}
}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 6, 2026
The registry name was verified with the GitHub account CloudCorpRecords, 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.0) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker 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.
Local video file tools as a CLI and a stdio MCP server in one bin. Probe a video for duration, dimensions and codecs; extract a thumbnail, frames or the audio track; trim, transcode and resize.
All work is built as ffmpeg/ffprobe argument arrays (execFile, never a shell string) behind an injectable executor, and probe results are parsed from ffprobe's JSON output — fields a file does not carry come back as null, never invented. This package bundles no ffmpeg: host runs use the host's binaries, and when they are absent the spawn error (ENOENT) is the tool error.
npx -y @reneturcios/videokit mcp
videokit mcp
videokit probe videokit thumbnail [timestamp-seconds] videokit audio videokit trim [duration-seconds] videokit resize videokit --version
Exit codes: 0 success, 1 ffmpeg error, 2 usage error.
| Tool | Purpose |
|---|---|
probe_video | Probe a local video file for duration, dimensions, codecs and format |
get_thumbnail | Extract a single frame of a video as a thumbnail image file |
extract_frames | Extract frames of a video as image files in an output directory at a given rate |
extract_audio | Extract the audio track of a video into an audio file |
trim_video | Trim a video to a segment starting at an offset, optionally with a duration |
transcode_video | Transcode a video to another container format |
resize_video | Resize a video to the given width and height |
MCP client config:
{
"mcpServers": { "videokit": { "command": "npx", "args": ["-y", "@reneturcios/videokit", "mcp"] } } }
docker run -i ghcr.io/cloudcorprecords/videokit # MCP server (ffmpeg unavailable in-image)
docker run --rm ghcr.io/cloudcorprecords/videokit --version
npm install
npm run build npm test
MIT license.