Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Beschreibung vom Entwickler (englisches Original)
Screen recorder and video editor. Agents record, trim, zoom, caption, add effects and export.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Der Entwickler hat in der Registry keine Installationsangaben gemacht. Sieh dir unten die README des Entwicklers an.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto getopenscreen bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (2.1.1) kam vor 19 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code.
In derselben Kategorie: Figma Context MCP, Claude Real Video, Figma MCP Server
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Make a demo video with one sentence in your AI agent:
Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreen --skill openscreen-demo -y`, then follow it to make a demo video of this feature.
A free, open-source desktop app for recording your screen and turning the result into polished product demos and walkthroughs.
[!NOTE]
This is OpenScreen, continued. Siddharth Vaddem created the project and archived the original repository after v1.5.0. Development moved here with his approval, under the same name and the same MIT license.
A raw capture goes in and comes out ready to post — on X, Reddit, YouTube, a docs page, or a landing page. That is the category Screen Studio defined; OpenScreen is the open-source entry in it, and not a clone.
100% free for personal and commercial use, with nothing held behind a paywall.
Project status. OpenScreen is under active development — expect rough edges and occasional breaking changes, including to the .openscreen project format and the CLI. Bug reports are welcome: open an issue.
OpenScreen ships a CLI for scripts, CI, and AI coding agents: record the screen headlessly, edit the .openscreen project JSON programmatically (zooms, annotations, trims), and render MP4/GIF with the full export pipeline — no visible windows, NDJSON output with --json.
openscreen record --duration 20 --project demo.openscreen --json
openscreen export demo.openscreen -o demo.mp4 --json
See the CLI reference.
Paste this into your AI agent (Claude Code, Codex, Cursor…):
Install the OpenScreen demo skill with `npx skills add getopenscreen/openscreen --skill openscreen-demo -y`, then follow it to add a video of this change to the PR.
The skill sets everything up: it installs OpenScreen if it is missing (once you agree), connects its MCP server, then asks you to open a new session and say *"continue the OpenScreen demo"*, the one step an agent cannot do for itself. By hand, in Claude Code, it is these two commands, where is the app's executable on your system (where to find it):
claude mcp add openscreen -- "<executable>" mcp
npx skills add getopenscreen/openscreen --skill openscreen-demo
From then on, ask: *"Add a video of this change to the PR."* The agent plans the storyboard, records the app, edits the take with OpenScreen's own editing tools, exports the MP4, checks it frame by frame, and attaches it to the pull request, where reviewers watch it in place. Ask for a launch demo instead and it drafts a post for X, which it publishes only once you say yes. Codex and the other clients are in AI editing.
Every platform has a recommended route below. On Windows that is the Microsoft Store; everywhere else it is the installer from the GitHub Releases page.
xdg-desktop-portal and PipeWire for native capture and system audio; recording still works without them through the browser-capture fallback, with fewer capabilities (see Platform differences)Full table and notes on older integrated graphics: system requirements.
Download the .dmg installer directly from the Releases page and drag OpenScreen into your Applications folder. Builds from 1.9.0 onward are signed with a Developer ID certificate and notarized by Apple, so Gatekeeper does not block them and no terminal step is needed.
On first launch, open System Settings > Privacy & Security and grant the two permissions OpenScreen needs: Screen Recording and Accessibility. Recording cannot start until both are granted.
[!NOTE]
macOS 15 and later re-ask for screen-recording permission periodically. That prompt comes from macOS itself and applies to every third-party screen recorder — it is not a sign that anything is wrong with your install or that an update broke something. Grant it again when asked.
[!NOTE]
Upgrading from a version older than 1.9.0? Those builds were not signed with a Developer ID certificate, and macOS ties Screen Recording and Accessibility grants to an app's signature — so it cannot tell the new build is the same app, and the permissions you granted the old one do not carry over. If the new version won't record even after you grant them, remove OpenScreen's existing entries under System Settings > Privacy & Security (both Screen Recording and Accessibility), then launch it again and grant them when prompted.
[!NOTE]
OpenScreen quits as soon as you pick what to record, or when the countdown starts? It is most likely a utility that quits apps once their last window closes, such as the Quit on close option of Vorssaint. It does not count OpenScreen's recording bar, which floats above other windows, so it quits OpenScreen whenever the bar hides or a source window closes. Add OpenScreen to that utility's exceptions, or turn the option off. The FAQ shows how to check which app asked OpenScreen to quit.
Recommended — Microsoft Store
Get OpenScreen from the Microsoft Store, or from a terminal:
winget install --source msstore OpenScreen
Microsoft signs the Store package during certification, so it installs with no security warning and updates itself.
Alternative — standalone installer
Download the .exe from the Releases page. Installers are provided for both x64 (Openscreen.Setup. -x64.exe) and ARM64 (Openscreen.Setup. -arm64.exe) — on an ARM64 device the x64 build runs under emulation and records poorly, so take the ARM64 one. Use this if you can't reach the Store — Windows LTSC, a locked-down work machine, an offline install, or if you want a specific older version.
[!NOTE]
The
.exeis not code-signed, so Windows SmartScreen shows "Windows protected your PC" and reports an unknown publisher. Choose More info → Run anyway to continue.
This is not a sign that something is wrong with the download: an unsigned installer earns SmartScreen's trust per file, so a brand-new build always starts out untrusted no matter how many people installed the previous one. Verifying the signature isn't an option here — there is nothing to verify. If you want the checked path, use the Store build above. If you use the
.exe, download it only from the Releases page linked here.
[!NOTE]
Recording bar not clickable in OpenScreen 2.0.0 on Windows 10? Run
setx OPENSCREEN_DISABLE_CONTENT_PROTECTION 1, quit OpenScreen from its tray icon, then start it again. The bar can then appear in your recordings. The FAQ explains how to undo it once the fix ships.
Four packages are published to the Releases page for each version. Pick the one that matches your distro:
Debian / Ubuntu / Pop!_OS (`.deb`)
sudo apt install ./Nur der Anfang wird gezeigt; den Rest findest du im Repo