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)
Let Claude listen to audio and watch video: transcribe, summarize and edit recordings and links.
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.
MEDIASENSE_COOKIES_FROM_BROWSERYou 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": {
"mediasense": {
"command": "uvx",
"args": [
"mediasense",
"mcp"
],
"env": {
"MEDIASENSE_COOKIES_FROM_BROWSER": "your-value"
}
}
}
}Run this in your terminal
claude mcp add mediasense --env MEDIASENSE_COOKIES_FROM_BROWSER=your-value -- uvx mediasense mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mediasense": {
"command": "uvx",
"args": [
"mediasense",
"mcp"
],
"env": {
"MEDIASENSE_COOKIES_FROM_BROWSER": "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": {
"mediasense": {
"type": "stdio",
"command": "uvx",
"args": [
"mediasense",
"mcp"
],
"env": {
"MEDIASENSE_COOKIES_FROM_BROWSER": "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.
MEDIASENSE_COOKIES_FROM_BROWSER envThese 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 joaoestella, 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.5.1) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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.
Give Claude ears and eyes. Claude can't listen to audio or watch videos on its own; with mediasense it can. Point at a voice message, podcast, recording or meeting, or paste a TikTok, YouTube or Instagram link, in Claude Code or Claude Desktop and ask in plain language. Claude can then transcribe it, summarize it, explain what happens, find the moment something is said, or edit it.
you: what does this voice message say? ~/Downloads/audio-from-maria.opus
you: summarize this https://www.tiktok.com/@someone/video/7350… you: what does he show at 0:30? and what tool is he talking about? you: clean up ~/Desktop/podcast.m4a — remove the "um"s and long pauses you: make short captions for ~/Videos/reel.mp4 you: put intro.mp3 under the first 5 seconds of talk.mp4, ducked
Real output for a 17-second TikTok by @elim.doc, shown with the creator's permission. Regenerate the animation with python docs/make_demo.py.
mediasense runs on your computer: it downloads the link, transcribes speech in ~99 languages with a timestamp for every word, picks key frames at scene changes, and hands Claude a transcript, a shot list and contact-sheet images. Nothing is uploaded anywhere.
Português 🇧🇷
Windows – paste in PowerShell:
irm https://raw.githubusercontent.com/joaoestella/mediasense/main/install.ps1 | iex
macOS / Linux – paste in a terminal:
curl -LsSf https://raw.githubusercontent.com/joaoestella/mediasense/main/install.sh | sh
Then quit Claude Desktop completely (tray/menu-bar icon → Quit), open it again and ask *"summarize this video: "*. The first transcription downloads the speech model (≈ 500 MB).
Prefer to read the script before running it?
irm https://raw.githubusercontent.com/joaoestella/mediasense/main/install.ps1 -OutFile install.ps1
notepad install.ps1 powershell -ExecutionPolicy Bypass -File .\install.ps1
(macOS/Linux: curl -LsSfO …/install.sh, read it, then sh install.sh.)
The installer only installs what is missing — Python 3.12 and FFmpeg via winget (Homebrew/apt on macOS/Linux) and pipx via pip — then pipx installs mediasense from this repository and runs mediasense setup. It stops at the first failed step.
Manual setup (no script)
winget install ffmpeg # macOS: brew install ffmpeg · Linux: sudo apt install ffmpeg
python -m pip install --user pipx python -m pipx ensurepath # then close and reopen the terminal python -m pipx install "mediasense[all]" mediasense setup -n # preview what setup will change mediasense setup mediasense doctor
Use python -m pipx … rather than plain pipx right after installing it: the pipx command only appears on PATH in a new terminal. No Git needed.
As a Claude plugin (skill + server in one)
The repository is also a Claude plugin: installing it adds both the mediasense tools and the skill that tells Claude when to use them. It starts the server with uv, so install uv first (winget install astral-sh.uv · brew install uv · curl -LsSf https://astral.sh/uv/install.sh | sh) plus FFmpeg if you don't have it.
In Claude Code:
/plugin install mediasense --marketplace joaoestella/mediasense
Any other MCP client (Cursor, VS Code, Windsurf…)
mediasense is a standard stdio MCP server, also listed in the official MCP Registry as io.github.joaoestella/mediasense:
{ "mcpServers": { "mediasense": { "command": "uvx", "args": ["mediasense", "mcp"] } } }
Or with a normal install: pipx install mediasense, then use mediasense mcp as the command.
One-click Claude Desktop extension (experimental)
Download [mediasense.mcpb](https://github.com/joaoestella/mediasense/releases/latest/download/mediasense.mcpb) and double-click it (or drag it into Claude Desktop → Settings → Extensions). No Python, pipx or FFmpeg needed: Claude Desktop sets up Python by itself, and FFmpeg is downloaded on first use. The first start takes a few minutes while it installs everything. This uses Claude Desktop's new "UV" extension type, so if it doesn't work on your version, use the installer above.
mediasense setup changesmcpServers.mediasense, to claude_desktop_config.json (%APPDATA%\Claude\ – or %LOCALAPPDATA%\Claude-Data\claude_…\ for the Microsoft Store app – ~/Library/Application Support/Claude/ on macOS, ~/.config/Claude/ on Linux; Claude Desktop → Settings → Developer → Edit Config opens the one your app uses). Everything else in the file is kept, and the previous file is saved next to it as claude_desktop_config.json. .bak. If the file isn't valid JSON, setup stops without touching it.claude mcp add --scope user mediasense -- \mediasense mcp.mediasense setup -n shows the exact changes without making them; --desktop or --code limits it to one app. To undo: remove the mediasense entry from the config file and run claude mcp remove mediasense --scope user.Updating on Windows and pipx says a file "is being used by another process"? Claude Desktop is still running the old server: Get-Process mediasense | Stop-Process -Force, then install again (the installer script does this for you).
Something not working? mediasense doctor checks FFmpeg, the speech model, the GPU, link downloads and the Claude connection.
mediasense comes with a skill: a short guide that makes Claude reach for mediasense whenever you paste a video link, instead of trying to open the page (TikTok & co. block that).
mediasense setup.Downloads/mediasense/), then in Claude open Settings → Skills and upload it. One time only; it syncs to all your devices.Note: Claude Desktop sends files you attach in the chat to the model, not to your computer, so give
mediasense a link or a file path instead (in Claude Code you can drag the file into the terminal).
The server adds ready-made prompts. In Claude Code they appear as /mcp__mediasense__summarize and so on.
| Prompt | Does |
|---|---|
summarize | gist, key points with timestamps, steps, names and links, call to action |
explain_video | shot-by-shot explanation, plus how the video is built (hook, structure) |
clean_up | remove fillers and long pauses, show the plan first, render after your OK |
subtitles | SRT captions, standard or short 1–3-word style for vertical video |
| Tool | What it does |
|---|---|
understand_media | one call: download link, transcribe, key frames + speech per shot, post title/description |
transcribe | speech → .transcript.json with word timestamps; vocabulary fixes brand names |
read_transcript, search_transcript | read a time range or find every time a phrase is said |
plan_edit, render_edit | cut phrases, passages, fillers, silences or ranges; preview, then render |
export_transcript | SRT, VTT, TXT, CSV, JSON |
place_audio | insert a clip at a timestamp (mix / duck / replace) |
watch_video, get_frame | contact sheets, or one frame at a given time |
media_info | duration, resolution, fps, streams |
check_job | result of long work: new videos and the first run reply "still working" and finish in the background |
Long work never hits Claude's tool time limit: if a video takes more than ~30 s (a long video on a CPU, or the very first run while the speech model downloads), the tool answers "still working" with a progress percentage and Claude checks back with check_job until it's done.
All tools accept a file path or a link. Links are downloaded once to ~/Downloads/mediasense (change with MEDIASENSE_HOME) and reused.
Everything also works without Claude:
mediasense understand "https://youtu.be/…" # transcript + shots + metadata, as text
mediasense transcribe talk.mp4 -l pt --vocab "Cloudflare, Claude" --also srt mediasense search talk.transcript.json "next quarter" mediasense edit talk.mp4 --fillers --silences 0.7 -n # -n = only show the plan mediasense edit talk.mp4 --fillers --silences 0.7 --srt --edl --fcpxml mediasense edit talk.mp4 --cut-between "let me check" "okay so" --cut-range 12:03-12:40 mediasense export talk.transcript.json captions.srt --words-per-cue 2 mediasense place video.mp4 voiceover.wav --at 0:12.5 --mode duck mediasense storyboard reel.mp4 mediasense fetch "https://www.tiktok.com/@…/video/…"
Edits never touch the original: results are written as .edited.* / .placed.*. EDL opens in Premiere, Resolve and Avid; FCPXML in Final Cut Pro and Resolve.
--vocab (Claude does this automatically when it can infer the names from the title or the screen).--verbatim when you want to cut them. Real words are protected per language ("um" is an article in Portuguese, so it is never cut there). Ambiguous words like "like", "tipo" or "né" are only removed if you list them.small model (base is faster, medium more accurate). No GPU? --backend openai sends the audio to an OpenAI-compatible transcription API instead (fast on any machine, but the audio leaves your computer). python -m pipx inject mediasense nvidia-cublas-cu12 "nvidia-cudnn-cu12>=9,<10" nvidia-cuda-runtime-cu12
(≈ 1.5 GB; needs a driver that supports CUDA 12 – mediasense doctor checks both). Restart Claude Desktop afterwards.
--backend whisperx (pip install "mediasense[whisperx]").mediasense runs entirely on your computer: no accounts, no analytics, no telemetry, and the author receives no data. It connects to the internet only to download the links you ask about, the speech model (first run), FFmpeg if it's missing, and – only if you choose the openai backend – to send audio to the transcription API you configure. Results stay on your disk until you delete them. When used from Claude, tool results (transcripts, key frames, metadata) are returned to the Clau
Only the beginning is shown; read the rest in the repo