MCP server
Use Screenify from Claude Desktop, Cursor, and other AI apps via the Model Context Protocol.
The screenify CLI ships a built-in MCP (Model Context Protocol) server, so AI apps that can't
run terminal commands — Claude Desktop, Cursor, ChatGPT's desktop developer mode, Windsurf and any
other MCP host — can record your screen and produce studio-styled videos by talking to Screenify
directly.
Using a coding agent that already runs shell commands (Claude Code, Codex)? You don't need MCP — those agents drive the CLI directly.
Zero-command setup (in the app)
The easiest path needs no terminal at all: open Screenify Studio → Settings → AI Assistants and click Connect AI assistants. It finds every AI client on your Mac and registers Screenify with each one — you'll see a per-app result right in Settings.
Then, in the Claude app: restart it, open a chat, and switch Screenify Studio on once in the chat input's + → Connectors menu — newly added connectors start toggled off, and the AI has no access to Screenify's tools until that switch is on.
One-click bundle (Claude Desktop)
Prefer a file to double-click? Download screenify.mcpb and open it —
Claude Desktop installs the connector, logo and all. The bundle carries no binary; it launches the
screenify CLI that ships inside Screenify Studio, so keep the app installed.
The bundle is the only install route that shows Screenify's logo. Connectors added through a config file (the button in Settings,
screenify mcp install,claude mcp add) get a generic icon — a config entry has no icon field, and current Claude Desktop builds ignore the icon the server advertises.
Add to Cursor or VS Code
One click each, if Screenify Studio lives in /Applications:
Installed somewhere else? Use the Settings button or the command below instead — both write the real path on your machine.
One-command setup
Prefer the terminal? With the CLI enabled on your Mac:
screenify mcp installThis registers the server with every AI client detected on your machine (Claude Code, Claude Desktop, Cursor) and backs up any config it touches. Restart the client — and in Claude Desktop, remember the one-time Connectors toggle described above. To target one client, preview first, or check what's already registered:
screenify mcp install --target cursor
screenify mcp install --dry-run
screenify mcp statusAny other MCP host can launch the server manually — command screenify, args ["mcp"], stdio
transport.
What the AI can do
| Tool | What it does |
|---|---|
check_readiness | Verify permissions before the first capture |
list_targets | Screens, windows, cameras, mics, booted iOS Simulators |
record_clip | One-shot: record for N seconds, style it (wallpaper, transitions, …) and even add cinematic effects — all in a single step |
start_recording / stop_recording | Record a screen, window, several windows composited, or an iOS Simulator |
get_recording_status | Check whether a recording is still running, and for how long |
export_video | Render a recording with studio styling — wallpaper, padding, device frames, photo mockups, transitions, aspect presets. Also takes a video or image file you already have |
record_web_demo | Drive a real browser over a URL (scripted or AI-driven) and produce a polished, auto-zoomed demo |
apply_effects | Add cinematic zoom, spotlight, callout effects and camera moves to a recording |
get_job_status / cancel_job | Long renders run as background jobs the AI polls |
inspect_project / list_recordings / get_schemas | Explore your library and the styling catalog |
open_result | Open the finished video — or the recorded project in the Screenify Studio editor — right from the chat |
A typical conversation in Claude Desktop: "record my main screen for 20 seconds, then export it vertical for TikTok with an orange wallpaper and a fade-in" — the AI chains the tools above and hands you back a finished MP4.
Things worth asking for
The AI translates plain language into the right flags, so you can ask for the finished thing:
- "Record a 15-second demo of this window and give it an orange background."
- "Put my last recording on a café desk photo with a slow push-in."
- "Record screenify.studio, scroll the landing page, and make it cinematic."
- "Take
~/Downloads/demo.mp4and style it as a vertical clip for TikTok." - "Frame my iOS Simulator recording as an iPhone 17 Pro Max and export a GIF."
The photo scenes come from Screenify's built-in catalog — you never have to supply an image or pick one in the app first.
Permissions
Screen capture uses macOS screen-recording permission from the app that hosts the AI — the
first time you record from Claude Desktop or Cursor, macOS will ask you to grant Screen Recording
to that app (System Settings → Privacy & Security). check_readiness walks the AI through
exactly what's missing. Exporting, effects and iOS Simulator recording work without it.