# StudioMeyer Video [Health: Active]

**Category:** 🎥 Multimedia Process  
**Repository:** https://github.com/studiomeyer-io/mcp-video  
**GitHub Stars:** 4  
**npm Downloads (last month):** 44  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/studiomeyer-video

## Description
Video production: recording, editing, effects, captions, TTS, screenshots. 8 tools.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "studiomeyer-video": {
    "command": "npx",
    "args": ["-y","@studiomeyer/mcp-video"]
  }
}
```

## Documentation

## What StudioMeyer Video MCP server does

The StudioMeyer Video MCP server exposes eight consolidated MCP tools for browser capture and video post-production. It belongs in the 🎥 Multimedia Process category and supports workflows that start with a website, an existing video, or a script.

Its tools cover:

- `video_record` for cinema, scroll, and multi-device website recordings, including frame-by-frame capture.
- `video_edit` for speed changes, cropping, reversing, keyframes, zoom and pan, and picture-in-picture.
- `video_color` for grading, effects, LUT presets, and chroma-key work.
- `video_audio` for extraction, mixing, ducking, music, and voice effects.
- `video_text` for SRT subtitles, Whisper captions, overlays, and animated text.
- `video_compose` for concatenation, introductions, social exports, beat synchronization, and templates.
- `video_speech` for ElevenLabs or OpenAI text-to-speech and narrated videos.
- `video_screenshot` for element-aware captures and page feature detection.

## How it works

StudioMeyer Video MCP server uses Playwright to operate browser pages and capture frames, then uses ffmpeg and ffprobe for video processing and encoding. Recording can include actions such as scrolling, hovering, clicking, typing, and waiting. Smart screenshots can identify interface areas such as chat widgets, pricing sections, and booking forms.

The tools can be combined into pipelines. For example, an agent can record a website, add captions and audio, then export the result for social platforms. A narrated workflow can combine a URL and scripted segments with AI voice generation. Existing local video files can also be edited, captioned, composed, or converted.

## Setup and configuration

The StudioMeyer Video MCP server requires Node.js 18 or newer, ffmpeg, ffprobe, and the Playwright Chromium browser. The package can run through `npx`, from a source checkout, or through a Claude Code stdio configuration. Stdio is the default transport; HTTP mode can be enabled with command-line flags or environment variables for a persistent service.

Generated files use `./output` by default and can be redirected with `VIDEO_OUTPUT_DIR`. If ffmpeg is not on `PATH`, set `FFMPEG_PATH` and `FFPROBE_PATH` to absolute binary paths. ElevenLabs TTS requires `ELEVENLABS_API_KEY`; OpenAI Whisper captions and OpenAI TTS require `OPENAI_API_KEY`.

HTTP deployments can configure `MCP_HTTP`, `MCP_PORT`, and `MCP_HOST`. `MCP_VIDEO_DEBUG` enables debug logging. `MCP_VIDEO_ALLOW_INTERNAL=1` permits URLs resolving to localhost, private, or metadata IPs and is documented for local development only.

## Limitations and notes

The StudioMeyer Video MCP server depends on local ffmpeg and Playwright browser installation, so those prerequisites must be available before use. ElevenLabs and OpenAI features are optional but need their respective API keys. The documented HTTP configuration binds to `127.0.0.1` by default. Internal URL access is guarded and should not be enabled in production.

_Full upstream README: https://allmcps.com/mcp/studiomeyer-video/readme_