Let AI agents record the Windows screen, watch it as frames, and edit it with ffmpeg
{ "mcpServers": { "io.github.tmhsdigital-screencast-mcp": { "command": "npx", "args": [ "-y", "@tmhs/[email protected]" ], "env": { "SCREENCAST_HOME": "<value>", "FFMPEG_PATH": "<value>", "FFPROBE_PATH": "<value>" } } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y @tmhs/[email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
SCREENCAST_HOME=<value> FFMPEG_PATH=<value> FFPROBE_PATH=<value> claude mcp add io.github.tmhsdigital-screencast-mcp -- npx -y @tmhs/screencast-mcp@0.37.0Run in a terminal.
{ "mcpServers": { "io.github.tmhsdigital-screencast-mcp": { "command": "npx", "args": [ "-y", "@tmhs/[email protected]" ], "env": { "SCREENCAST_HOME": "<value>", "FFMPEG_PATH": "<value>", "FFPROBE_PATH": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: SCREENCAST_HOME, FFMPEG_PATH, FFPROBE_PATH.
Screencast MCP runs locally over stdio.
Last checked 2026-10-26. Let AI agents record the Windows screen, watch it as frames, and edit it with ffmpeg
From the publisher
README is not crawled yet. Open the repository