Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Runs on your computer
Vibemovie
Overview
Description from the maker (original English)
Turns an agent coding session into a short recap video. Local-first.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 96/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Design, images & audio
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
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": {
"vibemovie": {
"command": "npx",
"args": [
"-y",
"vibemovie",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add vibemovie -- npx -y vibemovie mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vibemovie": {
"command": "npx",
"args": [
"-y",
"vibemovie",
"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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"vibemovie": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vibemovie",
"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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account pooriaarab, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Design, images & audioi
- More stars than 0% of the other 2785 servers in this category
- Published to the registry more recently than 19% of the other 2785 servers in this category
- Basic checks equal to or better than 100% of the other 2785 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Vibemovie safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.2.3) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Alternatives
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
Claude Real Video
Let any LLM watch a video locally — and search everything it has ever watched.
Runs on your computer
Figma MCP Server
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.
Runs in the cloud✓ mcp.figma.com
README from the maker
Open the README
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.
VibeMovie
Package · Setup · API example · Compare
VibeMovie is an open-source coding-session recap generator for developers and creators. It turns structured events into a self-contained animated HTML story through its local Hyperframes engine. An optional cinematic engine creates narrated MP4 output through WaveSpeed AI and FFmpeg. VibeMovie belongs to the Vibe Suite.
Install
npm install -g vibemovieRequires Node.js 18 or later. Includes TypeScript declarations and two direct runtime dependencies. The default Hyperframes engine needs no API key, browser automation, or FFmpeg installation.
Render your first recap
Create an input file:
cat > session.json <<'JSON'[ {"kind":"task-done","ts":1769500000000,"agent":"claude-code","payload":{"label":"Refactor auth","durationMin":18}}, {"kind":"tests-pass","ts":1769503600000,"payload":{"passed":42}}, {"kind":"pr-merged","ts":1769505100000,"payload":{"pr":42,"branch":"main"}} ] JSON vibemovie render session.json --title "Auth recap" --out recap.html
The CLI prints recap rendered and the output path. Open recap.html in a browser to play the story and scrub its timeline. No environment variables or credentials are required. The CLI does not load .env files. The input describes events; VibeMovie does not inspect your coding-agent history automatically.
How it works
JSON events -> normalize and sort -> scene compiler| +---------------------+---------------------+ v v Hyperframes (default) cinematic (explicit) embedded HTML/CSS/JavaScript WaveSpeed images + video + voice | | offline browser player FFmpeg -> MP4
Hyperframes rendering uses a local vibe-core runner with egress disabled. Cinematic rendering sends derived prompts, narration text, and intermediate media to WaveSpeed AI.
Why it exists
A terminal recording preserves activity. A recap selects tasks, test outcomes, diff totals, and pull-request milestones into a short story. VibeMovie compiles those supplied events with fixed templates. It does not need a language model to build the default recap. Remotion and asciinema address related video and terminal workflows with different inputs.
Compare
Checked 2026-10-14 against Remotion and asciinema CLI.
| Property | VibeMovie | Remotion | asciinema |
|---|---|---|---|
| Input | Structured coding events | React video compositions | Terminal session output |
| Scope | Template-based recap stories | Programmatic video and motion graphics | Terminal recording and streaming |
| Default artifact here | Self-contained HTML | Rendered compositions or embedded player | Asciicast recording |
| Authoring | JSON, Node.js API, agent tool | React components | Recorder CLI |
Coverage
| Integration or surface | Status | Source behavior |
|---|---|---|
| Hyperframes | Implemented; local | Embedded HTML, CSS, JavaScript, and scene data |
| WaveSpeed AI | Implemented; live API pending | Hosted generation orchestration |
| ByteDance Seedream v4 | Implemented via WaveSpeed; live API pending | Hero and face reference images |
| FLUX Kontext Max | Implemented via WaveSpeed; live API pending | Keyframe image edits |
| Kling v2.5 Turbo Pro | Implemented via WaveSpeed; live API pending | Image-to-video clips |
| ElevenLabs Eleven v3 | Implemented via WaveSpeed; live API pending | Narration synthesis |
| WaveSpeed video face swap | Implemented; best-effort | Optional intermediate face consistency step |
| FFmpeg | Implemented; external executable | Normalize, concatenate, grade, and mux cinematic output |
| Claude Code / OpenAI Codex / Google Gemini CLI | Event input only | Supply normalized JSON yourself; no harness-specific log reader |
| MCP | Implemented | One stdio render tool |
| OpenAI Sora / Replicate | — | No provider adapter shipped |
The source declares two engines, three ratios, three templates, six scene kinds, and five hosted model endpoints through one API service. Verification here covers source and local tests with injected cinematic dependencies. No paid API requests or credential checks were performed. An implemented endpoint is not a guarantee that a provider model remains available.
Common use cases
- Claude Code developers: export task and test events into an offline HTML recap.
- Codex maintainers: describe pull-request milestones in JSON for a release story.
- Gemini CLI creators: choose portrait Hyperframes output with
--ratio 9:16. - Node.js teams: call
buildScenesandrenderHyperframesinside an existing event pipeline. - MCP agents: render supplied events with the single
rendertool. - WaveSpeed users: opt into hosted cinematic generation with their own key and FFmpeg installation.
Features
- Scenes: title, tasks, diff, terminal, merge, and end; optional scenes depend on supplied data.
- Templates: documentary, speedrun, and meme control captions and pacing.
- HTML ratios:
16:9,9:16, and1:1. - Player: play/pause, timeline scrubbing, captions, and embedded scene data.
- Deterministic compilation: the same events and scene options produce the same local scenes.
- Cinematic pipeline: generated reference images, keyframes, clips, narration, and local MP4 assembly.
- Shot recipes: exported recipe data and deterministic selectors for custom callers; not an automatic CLI storyboard selector.
- Suite notification: rendering emits a best-effort
render-doneevent through vibe-core.
Runtime surfaces
vibemovie render [file.json|-] [--ratio 16:9|9:16|1:1][--template documentary|speedrun|meme] [--engine hyperframes|cinematic] [--out path] [--title name] vibemovie mcp vibemovie help vibemovie --help / -h vibemovie --version / -v / -V
render reads a file or stdin. Input accepts an event array or { "events": [...] }. Defaults are hyperframes, documentary, 16:9, and ./vibe-recap.html. Cinematic output defaults to ./vibe-recap.mp4.
vibemovie mcp starts the stdio Model Context Protocol (MCP) server with one tool:
| Tool | Required input | Optional input | Result |
|---|---|---|---|
render | events array | ratio, template, engine, title, out | HTML text, or a written output path |
Library example
Install with npm install vibemovie. Save this as recap.mjs and run node recap.mjs:
import { renderMovie } from 'vibemovie';const result = await renderMovie([ { kind: 'task-done', ts: 1769500000000, payload: { label: 'Ship auth' } } ], { title: 'Auth recap', out: 'recap.html' }); console.log(result.engine, result.path); // hyperframes recap.html
buildScenes(events, options) and renderHyperframes(scenes, options) are also exported for custom pipelines.
Delivery and behavior limits
Hyperframes produces animated HTML, not an MP4 or GIF. It does not record your screen or stream live agent activity. The CLI has no --session or --repo importer. Convert external recordings into the event schema before rendering. The scene compiler displays at most five task rows, four diff filenames, and five terminal lines. Terminal lines summarize supplied events; they are not a captured terminal transcript. Diff totals and test results reflect input claims, not an independent Git or test-run verification. Cinematic output is normalized to 1280×720 at 24 frames per second. HTML ratio options do not change that cinematic output size. Cinematic prompts use a fixed character and setting. There is no user-avatar selection or dynamic soundtrack engine. Missing WAVESPEED_API_KEY or FFmpeg triggers HTML fallback; recognized video filename extensions become .html. Runtime provider failures do not trigger a general HTML fallback. Failed clips may be skipped; all clips failing aborts the render. Prediction polling is bounded: normally 95 polls, narration 60, and face swap 140. Requests have no explicit network timeout. The face-swap step can fall back to the raw cut. Temporary cinematic work files remain on disk. Review input before rendering: hosted narration can include task labels, session names, and summary values.
Integration guides
- Portrait HTML recap:
vibemovie render session.json --ratio 9:16 --template speedrun --out portrait.html. - Event pipeline: pipe a JSON array into
vibemovie render --out recap.html. - Hosted cinematic recap: install FFmpeg, export
WAVESPEED_API_KEY, then runvibemovie render session.json --engine cinematic. - Environment file: load variables in your shell or launcher before starting the CLI; VibeMovie does not read
.envautomatically. - Agent setup: configure your MCP host to launch
vibemovie mcpover stdio.
Hosted rendering uses https://api.wavespeed.ai/api/v3. There is no separate ElevenLabs key in this pipeline.
Status
Version 0.2.4 is pre-1.0; APIs and generation behavior can change. Public case studies are not yet published. No public documentation site is configured; setup guidance is self-contained here. Source-only prototypes illustrate additional controls; they are not shipped web applications. Use GitHub issues for support; repository access may be required. For contributions, run npm ci, npm run build, npm run typecheck, npm test, and git diff --check.
FAQ
Which integrations are verified?
VibeMovie tests local rendering and cinematic orchestration with injected dependencies. Hosted endpoints have not been credential-checked in this rewrite.
Does VibeMovie provide a managed video service?
VibeMovie runs as a local package. Optional hosted generation uses your WaveSpeed API key and provider account.
How is VibeMovie different from Remotion?
VibeMovie compiles structured session events with preset scenes. Remotion provides React-based tools for custom video compositions.
How is VibeMovie different from asciinema?
VibeMovie renders a summary from supplied events. asciinema records and streams terminal output.
Can VibeMovie work offline?
VibeMovie renders Hyperframes HTML without remote assets or API keys. Its cinematic engine requires hosted API access.
Does VibeMovie export MP4 without credentials?
VibeMovie defaults to HTML when no cinematic credentials are available. MP4 generation requires a WaveSpeed key and FFmpeg.
Does VibeMovie read Claude Code or Codex logs automatically?
VibeMovie accepts JSON event input rather than scanning harness logs. Supply an event array through a file, stdin, the library, or MCP.
Can VibeMovie use my existing Sora or Replicate account?
VibeMovie has no Sora or Replicate adapter in this version. The cinematic pipeline calls fixed WaveSpeed model endpoints.
Are all output ratios available for cinematic MP4?
VibeMovie supports three ratios in Hyperframes HTML. Cinematic assembly currently normalizes video to 1280×720.
License
MIT.