Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Record your screen and export studio-styled demo videos on macOS, driven by your AI assistant.
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.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
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.
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 6, 2026
The registry name was verified against the domain screenify.studio (the registry checks domain ownership)
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 (2.2.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Dechonet MCP
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
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.
**Every other screen-related MCP server lets an AI *look at* your screen. This one lets it *make a video*.**
Ask Claude, Claude Code or Cursor for a demo and get back a finished file — recorded, styled and exported. No terminal, no flags, no editor.
"Record a 12-second demo of my landing page and put it on a café desk mockup."
Everything runs locally on your Mac. Nothing is uploaded.
https://github.com/user-attachments/assets/8c753dcb-0e53-4c00-acd6-0cd934b19415
Asked in a chat window; recorded, styled and exported by Screenify. No editor was opened.
Connect it to an AI assistant and ask for the finished video instead of driving the editor yourself:
Everything runs locally on your Mac. Nothing is uploaded.
Requires [Screenify Studio](https://www.screenify.studio/download) 2.2.0 or newer. The bundle carries no binary — it launches the CLI that ships inside the app.
This repository is also a Claude plugin. It bundles the MCP server with a skill that teaches Claude which Screenify flow to use for a request. In Claude Code:
claude --plugin-dir /path/to/screenify-mcp
The plugin's server runs locally, so it works in Claude Code and in Cowork sessions on your Mac. In a regular Claude chat, use the one-click bundle below instead.
What the plugin runs. scripts/screenify-mcp.sh looks for the screenify command that ships inside the Screenify Studio app (/Applications/Screenify Studio.app, or the copy the app installs at ~/.screenify/bin) and starts it as an MCP server over stdio. It downloads and installs nothing. If the app is missing, it returns an error that tells you where to get it.
Download screenify.mcpb and open it. Claude Desktop installs the connector.
Open Screenify Studio → Settings → AI Assistants → Connect AI assistants. It registers the server with every AI client it finds on your Mac. Or from a terminal:
screenify mcp install
Screenify is listed in the official MCP registry as studio.screenify/screenify, so clients that read the registry can find and install it without any of the steps above.
Full policy: [www.screenify.studio/privacy](https://www.screenify.studio/privacy)
In short, for this MCP server specifically:
Issues with the MCP server or the app: support@screenify.studio
This repository — the Claude plugin (a manifest, a launcher script and a skill), the MCP bundle (screenify.mcpb: a manifest, a launcher script and an icon) and its documentation — is MIT licensed.
Screenify Studio itself is proprietary software and is not covered by that license. The app provides the MCP server, the recording pipeline and the export engine; this repo only ships the small bundle that launches it.