mcpField
S
Screen Recorder MCP

Screen Recorder MCP

Local
github.comMedia & Design0Updated 2d ago

About Screen Recorder MCP

Screen Recorder MCP lets AI agents record real browser pages and turn them into vertical videos, for people producing product demos or interface clips. It records actual UI content and composes captions, callouts, zooms, music, and end cards locally.

Key features

  1. 01Record browser pages over CDP
  2. 02Compose vertical clips from recordings
  3. 03Add device frames and callouts
  4. 04Apply captions, zooms, and end cards
  5. 05Mix music with audio ducking

Use cases

  1. 01Create a vertical product demo from a live page
  2. 02Record interface walkthroughs for publishing
  3. 03Add captions and callouts to a browser recording

MCP support

It is an MCP server that exposes recording status, start/stop, file listing, and clip composition tools to MCP clients. Agents can invoke `compose_clip` to create a finished video.

Configuration

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

mcp.json · Universal config
{
"mcpServers": {
"robert0303-c-screenrec-agent": {
"command": "npx",
"args": [
"-y",
"screenrec-agent"
]
}
}
}
Run commandnpx -y screenrec-agent

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
npmscreenrec-agent0.1.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Screen Recorder MCP

Let your AI agent record a real browser page and cut it into a publishable vertical video.

By xukunAI · an MCP server for Claude Code, Cursor, Codex and Hermes. Your agent records a page over CDP (no browser extension, no permission dialog), then composes the clip: device frame, held-frame callouts, punch-ins, captions, music with real ducking, end card.

Everything runs locally. No upload, no API key, no cloud render.

录制 → 设备框 → 冻结圈注 → 局部放大 → 字幕 → 结尾卡 → 成片

Why this exists

Every "AI video" tool generates pixels and hopes the text survives. This one doesn't generate anything: it records your actual UI and draws text with a font engine. Every digit is your real number.

The agent-facing part is the point: an agent can produce a finished clip as a tool call, not a chat suggestion.

Tools

ToolWhat it does
recorder_statusrecording state, bytes, bridge status
recorder_startstart recording a tab (Chrome requires one human click — see below)
recorder_stopstop and save to Downloads
recorder_fileslist recent recordings
compose_clipthe actual product: record → finished video

compose_clip takes captions, annotations (held-frame callouts), focus (punch-ins), end_title, music, frame (phone/browser), pip (picture-in-picture).

Install

npx (recommended) — works in Claude Code, Cursor, Codex, Hermes and any MCP client:

{
  "mcpServers": {
    "screen-recorder": {
      "command": "npx",
      "args": ["-y", "screenrec-agent"]
    }
  }
}

Then verify the install:

npx -y screenrec-agent --selftest

First run downloads the agent (~33 MB) and a pinned ffmpeg build (~201 MB) into %LOCALAPPDATA%\screenrec-agent\bin. The cache is reused afterwards, and upgrading the launcher re-downloads only the agent — ffmpeg is not fetched again. Downloads resume and retry on a dropped connection instead of failing silently.

Or use the exe directly. Download screenrec-agent.exe from the latest release, put ffmpeg.exe beside it (only compose_clip needs ffmpeg), and point command at the exe.

Published in the official MCP Registry as io.github.Robert0303-C/screenrec-agent.

Pricing

FreeFull — $39 once
recorder_* — record with your agentunlimited, foreverunlimited
compose_clip — turn a recording into a finished clip24 hours / 5 clipsunlimited
Runs locally, nothing uploadedyesyes

The trial starts on your first successful compose, not on install. When it ends, compose_clip returns license_required with a purchase link — recording keeps working, nothing is deleted, nothing crashes. Check what is left with screenrec-agent --status, unlock with screenrec-agent --activate <KEY>.

The only network call is activation itself. Trial state lives on your machine (three copies, clock rollback detection) because the alternative is a server that watches you use it. Deleting all three copies is equivalent to a fresh install — offline software cannot prevent that, and we would rather be honest about it than ship surveillance.

Buy: https://creem.io/store/screenrec-agent · xukun.online

The one gesture Chrome insists on

chrome.tabCapture needs activeTab, and activeTab only comes from invoking the extension on that tab. No script can fake it (verified: even a trusted CDP click inside an extension page fails). So:

  • Page recording (CDP) — fully autonomous, no click, no extension
  • Desktop + microphone recording (extension) — the human clicks the toolbar icon once, the agent handles everything after

Requirements

  • Windows 10/11 x64
  • ~300 MB disk
  • An MCP client

Roadmap

  • CDP recording, freeze-frame callouts, punch-ins
  • Device frame, captions, end card, music ducking, picture-in-picture
  • Voice-over (piper, EN + ZH) — Full edition
  • macOS

License

Commercial. Source available for review; redistribution of the packaged binary is not permitted.

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.