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)
VIVID (vividai.tv) AI studio: product photos, videos, voice, music and timelines for e-commerce.
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.
AuthorizationValues 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 …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http vivid https://mcp.vividai.tv/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vivid": {
"url": "https://mcp.vividai.tv/mcp",
"headers": {
"Authorization": "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": {
"vivid": {
"type": "http",
"url": "https://mcp.vividai.tv/mcp",
"headers": {
"Authorization": "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 address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
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 9, 2026
The registry name was verified with the GitHub account loopotv, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 303 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.36.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
MCP server for VIVID — the AI content studio for e-commerce. Connect your VIVID account to Claude Desktop, Claude Code, Cursor or any Model Context Protocol client and generate images and videos, browse your gallery and manage jobs from the chat.
| Tool | What it does | |
|---|---|---|
vivid_whoami | Account linked to the key: plan, credits | |
vivid_usage | Monthly usage vs plan limits | |
vivid_buy_credits | Link where the user buys a credit pack or turns on auto top-up — the agent never pays, the user confirms in the browser | |
vivid_list_models | Image / video / LLM models with prices and capabilities | |
vivid_generate_image | Text-to-image (with optional product / person / context references), waits for the result | |
vivid_generate_video | Start a video (Seedance 2.5, Kling O3, MiniMax H3, Gemini Omni, LTX, Grok…) | |
vivid_job_status | Poll a job, get the asset and download URL | |
vivid_list_jobs | Recent generations | |
vivid_list_assets · vivid_get_asset | Browse the gallery | |
vivid_download_asset | Save an asset to a local folder | |
vivid_share_asset | Publish an asset and get a share link, toggle favorite | |
vivid_upload_file | Upload a local file or URL to use as reference / start frame / audio | |
vivid_list_references | Saved products (from product analysis) and testimonials / characters with names and ids — use the names in vivid_generate_image products / testimonials, like #Product / @Testimonial in the app | |
vivid_analyze_product · vivid_create_testimonial | Save a product from a photo (free, plan quota) or create a reusable testimonial from three photos or attributes (50 credits) — both then usable by name | |
vivid_list_voices | TTS providers and preset voices with credit cost | |
vivid_chat | One chat completion on VIVID's LLM routing — Grok, Claude, OpenAI GPT, Kimi (Wavespeed) | |
vivid_generate_music · vivid_music_status · vivid_list_music_providers | Unique track from a brief — Suno V6 (default, 6 credits for two takes, exact length for instrumentals) or MiniMax Music 3.0 (14 credits, length is a hint, trim in the editor); vocals optional, charged when ready. Rendering takes 20 s–3 min: the tool waits up to waitSec, then returns a taskId for vivid_music_status | |
vivid_analyze_audio | Tempo (BPM, beat grid) and transient peaks of a music/voice file, computed server-side (free): the cut points for a dynamic montage, also used automatically by CUT_TO_BEAT (grid beats \ | peaks) |
vivid_search_sounds | Search Freesound.org for existing music, loops and sound effects (free). Commercial-safe licenses only by default (CC0, CC BY), with a ready attribution line for CC BY; returns MP3 preview URLs to drop into a timeline | |
vivid_transcribe | Speech-to-text (Deepgram Nova-3, free): per-word timestamps, readable cues, SRT/VTT export — from an asset, URL or local file | |
vivid_retouch | Edit ONE object of an image (text target, region or mask), rest byte-identical — 2–6 credits | |
vivid_compare_product | Visual QC of a render vs the SKU photo: match score, verdict, differences, fixPrompt — 1 credit | |
vivid_product_sheet | Reads the reference sheet of a saved product and the price of a new one (free) | |
vivid_create_product_sheet | Makes the reference sheet: front, two angles and worn, each checked against the real photo (one free redo, refund if it still fails) — 13 credits, first one free on the free plan | |
vivid_generate_voice | Text-to-speech: Gemini 3.1 Flash presets, MiniMax Speech 2.8 HD (presets, emotions, and voices the account holder saved in the VIVID web app after confirming they own the voice), OmniVoice voice design, Deepgram. It does not clone a voice from an audio file or URL | |
vivid_list_projects | Your projects | |
vivid_list_editor_projects | Saved video-editor timelines | |
vivid_create_editor_project · vivid_get_editor_project · vivid_edit_timeline | Build and edit video-editor timelines headless (clips, trims, speed, transitions, 16:9↔9:16, texts, masks, keyframes) with the same engine as the web editor — see *Timeline editing* | |
vivid_render_project · vivid_render_status | Queue an MP4 render of an editor project and poll it (see *Rendering* below) | |
vivid_record_ui | Screen-record a scripted walkthrough of vividai.tv (or any site) with a local Chromium — cursor, smooth moves, click ripples — and upload it as a video asset (see *UI recording* below) |
| How | Needs Node? | Local-only tools (vivid_download_asset, vivid_record_ui, local paths) | |
|---|---|---|---|
| Remote | https://mcp.vividai.tv/mcp + Authorization: Bearer vk_… | no | no |
| Connector (Claude.ai) | https://mcp.vividai.tv/mcp with OAuth — no key to paste | no | no |
| Connector (ChatGPT) | https://mcp.vividai.tv/chatgpt with OAuth — no key to paste | no | no |
| Claude Code plugin | /plugin install vivid@vivid — OAuth, plus the VIVID skills | no | no |
| Claude Desktop extension | download vivid-mcp.mcpb, double-click, paste the key | no (bundled runtime) | yes |
| Local (npx) | npx -y vivid-mcp with VIVID_API_KEY | Node.js 20+ | yes |
| Command line | npx -y vivid-mcp call ' ' with VIVID_API_KEY — no MCP client | Node.js 20+ | yes |
The same server runs as a Cloudflare Worker at https://mcp.vividai.tv/mcp (Streamable HTTP, stateless). Send your API key on every request:
# Claude Code
claude mcp add --transport http vivid https://mcp.vividai.tv/mcp --header "Authorization: Bearer vk_xxx"
// Cursor and other clients that take a URL + headers
{ "mcpServers": { "vivid": { "url": "https://mcp.vividai.tv/mcp", "headers": { "Authorization": "Bearer vk_xxx" } } } }
GET https://mcp.vividai.tv/ answers with the version and the endpoint. Files must be public URLs (vivid_upload_file accepts a URL); outputDir / outputPath are ignored.
Clients that cannot send a header authenticate with OAuth 2.1 instead. Add a connector with the URL https://mcp.vividai.tv/mcp (Claude.ai → Settings → Connectors → Add custom connector) or https://mcp.vividai.tv/chatgpt (ChatGPT → Settings → Connectors → Create) and pick OAuth. The client discovers /.well-known/oauth-protected-resource, registers itself (dynamic client registration) and sends you to vividai.tv/oauth/consent, where you sign in and click Authorize. Each connector gets its own credential (vc_…, never your API key) that acts on your assets and credits but cannot change the password, rotate the API key or delete the account; revoke it any time from Settings → Connected apps.
/chatgpt serves the same tools under OpenAI's plugin guidelines: no vivid_buy_credits (an out-of-credits error points to the informational page vividai.tv/credits, which has no checkout or upgrade button), no vivid_chat, no photos or recordings of a real person as inputs (vivid_create_testimonial takes attributes only, vivid_generate_image has no modelImageUrls, vivid_generate_video takes only audio made by vivid_generate_voice / vivid_generate_music and only gallery videos as references; every other image — frames, references, product and scene photos, retouch sources, vivid_upload_file — goes through the API's person check, which refuses a recognisable face). Replies leave out timestamps, raw project dumps, API paths and provider details.
This repo is also a Claude Code plugin and its own marketplace. It connects to the remote server with OAuth (no key to paste) and adds the skills in skills/ (product photos, product video, brand cast):
/plugin marketplace add loopotv/vivid-mcp
/plugin install vivid@vivid
Then run /mcp, pick vivid and authenticate: the browser opens vividai.tv/oauth/consent. The manifest lives in .claude-plugin/; its version must match package.json (a test checks it), because installed plugins only update when it changes. Check it with claude plugin validate --strict ..
Download vivid-mcp.mcpb and open it with Claude Desktop: it installs the server with its own Node runtime and asks for your API key (stored by Claude as a secret). Built with npm run build && npx @anthropic-ai/mcpb pack from manifest.json.
claude mcp add vivid -e VIVID_API_KEY=vk_xxx -- npx -y vivid-mcp
claude_desktop_config.json:
{
"mcpServers": { "vivid": { "command": "npx", "args": ["-y", "vivid-mcp"], "env": { "VIVID_API_KEY": "vk_xxx" } } } }
Same command: npx -y vivid-mcp with VIVID_API_KEY in the environment.
The same tools run from a shell, through an in-memory MCP client — same arguments, same validation, same results. This is what the vivid-studio skill uses in agents that have a terminal but no MCP connection.
export VIVID_API_KEY=vk_xxx
npx -y vivid-mcp tools # every tool with its title npx -y vivid-mcp schema generate_image # description + JSON schema of the arguments npx -y vivid-mcp call whoami # the vivid_ prefix is optional npx -y vivid-mcp call generate_image '{"prompt":"…","model":"nano-banana-2"}' npx -y vivid-mcp call edit_timeline @args.json # or - to read stdin
The tool's text result goes to stdout; the exit code is 1 when the tool reports an error.
| Variable | Required | Default |
|---|---|---|
VIVID_API_KEY | yes | — |
VIVID_API_URL | no | https://vivid-api.vividoai.workers.dev |
vivid_create_editor_project / vivid_edit_timeline run the VIVID editor headless (vivid-editor-core, the same store and AI-command orchestrator the web editor uses) and save the project to your account, so anything you build here opens in vividai.tv/tools/editor and renders with vivid_render_project. Commands are { type, payload } objects (ADD_CLIP, UPDATE_CLIP, SPLIT_CLIP, SET_TRANSITION, SET_CANVAS_PRESET, ADD_TEXT, SET_ANIMATIONS, ADD_EFFECT, SET_MASK…) — the tool descriptions list them. Media is imported by VIVID asset id, URL or local path.
vivid_record_ui drives a local Chromium through Playwright and records the session: you pass a list of steps (goto, click, hover, type, fill, press, scroll, wait, hide, evaluate, with Playwright selectors) and get back a crisp 2× vide
Only the beginning is shown; read the rest in the repo