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)
MCP Server for video enhancement and image segmentation (SAM3)
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.
API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"media": {
"command": "npx",
"args": [
"-y",
"@avclabs.ai/media-mcp"
],
"env": {
"API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add media --env API_KEY=your-value -- npx -y @avclabs.ai/media-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"media": {
"command": "npx",
"args": [
"-y",
"@avclabs.ai/media-mcp"
],
"env": {
"API_KEY": "your-value"
}
}
}
}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": {
"media": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@avclabs.ai/media-mcp"
],
"env": {
"API_KEY": "your-value"
}
}
}
}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 avclabs, 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.
You need to fill in: API_KEY
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.2.0) reached the registry 6 months 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.
English | 中文
MCP servers wrapping the AVCLabs hosted media services, published as one function per npm package so an MCP client session only loads the tool definitions it actually uses.
| Package | Function | Tools | Bin |
|---|---|---|---|
@avclabs.ai/video-mcp | Video enhancement | create_task, get_task_status, enhance_video_sync | video-mcp |
@avclabs.ai/image-mcp | Image enhancement / colorization / denoising | enhance_image_sync, colorize_image_sync, denoise_image_sync, get_image_task_status | image-mcp |
@avclabs.ai/sam3-mcp | SAM3 image segmentation | sam3_predict, get_sam3_task_status | sam3-mcp |
@avclabs.ai/media-mcp | Legacy all-in-one (all 9 tools) | everything above | media-mcp |
@avclabs.ai/media-mcp-core | Shared internal library (not an MCP server) | — | — |
get_*_task_status variant present, the model picks tools more reliably.The legacy all-in-one @avclabs.ai/media-mcp keeps working unchanged for existing configurations; see its README for a migration note.
Every server is a stdio MCP server over npx. For example, image tools only:
{
"mcpServers": { "image-mcp": { "command": "npx", "args": ["-y", "-p", "@avclabs.ai/image-mcp@latest", "image-mcp"], "env": { "API_KEY": "your-api-key" } } } }
Each package ships exactly one bin named like the package, so plain npx -y also works; the snippets use the explicit -p form because it pins the exact binary regardless of how a package's bin set evolves. Each package README (video, image, SAM3) has full install instructions for Claude Code, Cursor, and global installs, plus the configuration variables it reads.
All packages share one API_KEY and the same production host defaults (https://mcp.avc.ai/enhance and https://mcp.avc.ai/sam).
packages/
core/ shared library: tool registration, polling, TOS upload, config video-mcp/ video enhancement server (3 tools) image-mcp/ image processing server (4 tools) sam3-mcp/ SAM3 segmentation server (2 tools) media-mcp/ legacy all-in-one server (9 tools)
Domain vocabulary shared across the packages lives in CONTEXT.md; decisions are recorded in docs/adr/.
npm ci # installs workspaces and builds every package
npm test # rebuild + run all package tests npm run release:verify # metadata gate + audit + tests + pack dry-run node scripts/e2e-check.mjs # stdio E2E for all four server entries
To iterate on one package: build core once (npm run build -w packages/core), then run npm run dev -w packages/ (tsc --watch) in another terminal.
Maintainers: see the release guide for publish order (core first), versioning, tags, and smoke tests. Publishing is manual from a clean checkout; the CI workflow runs the same verification gate on Node 22.
MIT License — see LICENSE.