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)
Local-first video editor for AI agents: 59 tools for auto-edit, shorts, captions, music and QC.
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": {
"ai-edit-studio": {
"command": "npx",
"args": [
"-y",
"ai-edit-studio",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add ai-edit-studio -- npx -y ai-edit-studio mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ai-edit-studio": {
"command": "npx",
"args": [
"-y",
"ai-edit-studio",
"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": {
"ai-edit-studio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ai-edit-studio",
"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 8, 2026
The registry name was verified with the GitHub account laaielichter, 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.11.0) reached the registry 4 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:↓ Downloads per weeki★ 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.
Your footage. Your story. Your studio. A local-first video editor for creators and their AI agents. Project website · Get started · Connect your agent · Contribute
A local-first video editor for creators, game developers and their agents. One engine with a pro timeline for people and the same 59 tools for agents (MCP, HTTP/OpenAPI, CLI). Your footage never leaves your machine; originals are only read.
*Formerly Game Trailer Studio. Existing projects, storage paths, GAME_TRAILER_STUDIO_* settings and the Start-Game-Trailer-Studio.* scripts keep working. The Dutch history of this README lives in docs/README.nl.md.*
New in 0.10 — music engine
studio_music): an original track in one of six styles (pop drop, trap, house, lo-fi, synthwave, cinematic trailer), made on this computer from synthesised instruments — no samples, no internet, free to use. It is exactly as long as your edit, its drops land exactly on your cuts (or markers named *drop*) and it ends with a final hit on the last frame. Same seed = same track, *New variation* = a new melody and groove. The beat grid is exact, so *Snap cuts to beat* uses the real beats. Optional stems (drums, bass, music, effects).New in 0.9 — polish
New in 0.8 — long edits
New in 0.7
studio_wait, live SSE events and recipes (multi-step workflows in one call).New in 0.6
For editors (open http://127.0.0.1:32146/; interface in English or Dutch, switch top right)
?.For agents — see [AGENTS.md](AGENTS.md), setup for Claude, Cursor, OpenAI Codex, the OpenAI API, n8n and others in [docs/INTEGRATIONS.md](docs/INTEGRATIONS.md), and fixes in [TROUBLESHOOTING.md](TROUBLESHOOTING.md).
| Door | Entry |
|---|---|
| Claude Code plugin | /plugin marketplace add → /plugin install ai-edit-studio@ai-edit-studio (tools + workflow skills + video-director agent) |
| OpenAI Codex | node cli.mjs codex-setup (or the Codex plugin in plugins/ai-edit-studio) — tools + the same skills |
| OpenAI API | examples/openai/ (Responses API, Agents SDK); GET /api/agent/tools?format=openai |
| MCP (stdio) | claude mcp add ai-edit-studio -- node mcp.mjs |
| HTTP | GET /api/agent/tools, POST /api/agent/call, POST /api/agent/tools/{name} |
| OpenAPI 3.1 | GET /api/openapi.json |
| CLI | node cli.mjs studio --request file.json [--wait] |
One call from footage to renders: studio_auto_edit. Text-based editing: studio_transcribe, studio_transcript, studio_text_edit. Plus studio_reframe, studio_publish_pack, studio_brand. Atomic studio_edit batches on stable clip ids (with dryRun), studio_timeline + studio_storyboard to see the edit, studio_review with machine-applicable fixes, beats, highlights, styles, caption import, history/diff/restore, duplicate and render. Every agent change is a revision with the agent's name.
With npm (Node 20+ and FFmpeg needed):
npm install -g ai-edit-studio
ai-edit-studio install # data folder + connects Claude Code, Codex, Claude Desktop and Cursor ai-edit-studio serve # starts the editor on http://127.0.0.1:32146
As an MCP server for an agent, without installing anything first: claude mcp add ai-edit-studio -- npx -y ai-edit-studio mcp (the same command works in Cursor, Claude Desktop and Codex configs). Registry name: io.github.laaielichter/ai-edit-studio.
From the download zip: unzip, double-click Install-AI-Edit-Studio.cmd (macOS/Linux: ./install.sh) and follow INSTALL.md. It sets up the data folder and connects Claude Code, OpenAI Codex, Claude Desktop and Cursor in one go.
From source:
Requirements: Node 20+ and an FFmpeg build with libx264 (tested with FFmpeg 9.0.1 on Windows and 6.1 on Linux; NVENC used when available).
# double-click Start-Game-Trailer-Studio.vbs (hidden server, opens the browser)
npm start node cli.mjs doctor # checks FFmpeg, encoder, storage and the (optional) speech engine node cli.mjs speech-setup --model base # optional: local speech recognition (whisper.cpp + model, ~200 MB)
FFmpeg/ffprobe are found on PATH, in tools/ffmpeg/bin under the app or data folder, or via FFMPEG_PATH / FFPROBE_PATH.
Storage. Projects and renders go to the data folder: the one you chose in the installer, otherwise Documents\AI Edit Studio on Windows and .studio-data next to the app on macOS/Linux. To pick another folder:
./Start-Game-Trailer-Studio.ps1 -DataRoot 'D:\AI-Edit-Studio'
The server binds to 127.0.0.1:32146 only (GAME_TRAILER_STUDIO_PORT to change). The old capture console is at /legacy.html.
Only the beginning is shown; read the rest in the repo