mcpField
A
AIOProductOS Studio

AIOProductOS Studio

Local
aioproductos.comMedia & Design3Updated 14w ago

About AIOProductOS Studio

AIOProductOS Studio is a locally run MCP server that records scripted walkthroughs of web apps and produces videos and screenshots. It is intended for product demos and launch materials, with guided cursor motion, callouts, captions, and scene transitions.

Key features

  1. 01Record scripted web app walkthroughs
  2. 02Add captions, voice-over, and callouts
  3. 03Use smooth zooms and camera moves
  4. 04Export MP4 or GIF
  5. 05Capture high-resolution screenshots

Use cases

  1. 01Create product feature demo videos
  2. 02Make changelog GIFs
  3. 03Record flows in logged-in app areas
  4. 04Capture a launch-page hero image

MCP support

The MCP server exposes tools for browser recording, interaction, captions, narration, screenshots, and video export; recording runs locally.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-aioproductos-mcp-studio": {
"command": "npx",
"args": [
"-y",
"@aioproductoscom/mcp-studio"
]
}
}
}
Run commandnpx -y @aioproductoscom/mcp-studio

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@aioproductoscom/mcp-studio0.2.3

Tools

14

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
themeobjectNoVisual theme for overlays/transitions — use the recorded product's brand.
theme.bgstringNoApp background color, e.g. '#0d1117' (default '#101014').
theme.fontstringNoOverlay font stack (default system-ui).
theme.textstringNoOverlay text color (default near-white).
theme.brandstring|nullNoBrand name on transition cards; null for none.
theme.accentstringNoAccent for rings/captions/cursor, e.g. '#4f8cff'.
widthnumberNoViewport width in px (optional; default 1280).
heightnumberNoViewport height in px (optional; default 720).
cookiesarrayNoCookies to pre-set, e.g. your consent cookie so banners never mount (optional).
show_cursorbooleanNoVisible on-screen cursor that glides to targets (default true).
color_schemeenumNoprefers-color-scheme for the page (default dark).dark | light
hide_selectorsarrayNoCSS selectors to hide from frame 1 (chat bubbles, cookie banners, dev overlays).
storage_state_pathstringNoPath to a Playwright storageState JSON for logged-in recording (optional).

Details

From the project README

AIOProductOS Studio · MCP

Your AI teammate becomes your product videographer. Studio is an MCP server that records scripted walkthroughs of your own web app — a visible cursor that glides to every click, camera punch-ins, highlight callouts, storyline captions, designed scene transitions — and takes marketing-grade screenshots. Tell your AI host what story to shoot; get back a share-ready MP4.

The videos PMs hate making — demo clips, explainers, changelog GIFs, launch screenshots — become one prompt.

Free · MIT · runs 100% locally (your browser, your URLs, your logged-in session — nothing is uploaded anywhere). By AIOProductOS, built from the same pipeline we use for our own launch videos.

Install

# Claude Code
claude mcp add studio -- npx -y @aioproductoscom/mcp-studio

# Cursor / Codex — .mcp.json
{ "mcpServers": { "studio": { "command": "npx", "args": ["-y", "@aioproductoscom/mcp-studio"] } } }

Requirements: Node 18+, Playwright Chromium (npx playwright install chromium, one-time), and ffmpeg on PATH for MP4/GIF export (brew install ffmpeg — without it you still get the raw WebM).

Use

Then just direct the film:

"Record a 30-second walkthrough of https://app.example.com — theme it to our brand (#0d1117 bg, #f97316 accent), open on the dashboard with the title 'Meet Example', caption the three key features, zoom in on the analytics chart, and end with 'Start free · example.com'. Also grab a hero screenshot."

Your host runs the shoot tool by tool; files land in ./studio-output/.

The tools

ToolWhat it does
studio_startopen a themed recording browser (viewport, brand colors, logged-in state)
studio_gotonavigate behind a designed title card — no loading flashes on tape
studio_click / studio_typecursor glides to the target; typing is human-paced
studio_scrollcubic-eased scroll, never a jump cut
studio_captionbottom-left storyline caption (the "voiceover" in text)
studio_narratespoken voice-over with NO on-screen caption; holds the shot under the line
studio_highlightaccent ring + label callout around any element or visible text
studio_zoomsmooth camera punch-in on a metric, button, or result
studio_holdhold the shot (micro-drift keeps frames flowing)
studio_end_cardclosing glass card: title, subtitle, CTA URL
studio_screenshothigh-DPI PNG of the frame, an element, or the full page
studio_finishstop, auto-remove dark frames, export MP4 (+ optional GIF)
studio_cancelabandon the take

Recording logged-in areas

Studio never sees your credentials. Save a Playwright storageState once (npx playwright codegen --save-storage=auth.json https://app.example.com), then pass storage_state_path: "auth.json" to studio_start.

Keeping junk off the tape

  • Cookie banner? Pass your consent cookie via cookies so it never mounts.
  • Chat bubble / dev overlay? List selectors in hide_selectors — hidden from frame 1.
  • Wrong flash color on page loads? Set theme.bg to your app's real background.

Why it looks good (the hard-won part)

No white flash on page commits (the theme background paints before any page CSS), no black frames (navigations hide behind designed title cards, and residual dark frames are detected and cut deterministically with ffmpeg), no stutter (every camera move is compositor-friendly easing), and action that reads on camera (a visible cursor glides to every target before it acts).

Links

MIT © AIOProductOS Inc.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.