MCP servers › io.github.Ashutos1997 › ffmpeg-mcp-server
MCP server · registry snapshot 2026-10-24
io.github.Ashutos1997/ffmpeg-mcp-server
FFmpeg & FFprobe media processing toolkit for video, audio, and social formats — the publisher's description
Summary
io.github.Ashutos1997/ffmpeg-mcp-server is a local MCP server listed in the official MCP registry at version 0.5.0.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: no download figure available
- Not ranked by stars: 2 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Topic
- media-and-designAI-classified
- Last tested
- not tested
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.5.0, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)
- First listed version
- 2026-10-22 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, 2026-10-22 to 2026-10-23; 2 in the 90 days before the 2026-10-24 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.5.0· 2026-10-230.4.2· 2026-10-22
- Registry data
- snapshot 2026-10-24
- Package and repository
- checked 2026-10-24
Changes since the last refresh
Version 0.4.2 (published 2026-10-22) → 0.5.0 (published 2026-10-23), between the registry lists of 2026-10-23 and 2026-10-24.
The publisher’s GitHub release note for v0.5.0 (“v0.5.0 - Universal GPU Acceleration, MCP Progress, Cancellation & 4 New Tools”), published 2026-10-23.
Read the release note (the publisher’s text, shown as plain text)
### What's New in v0.5.0 #### 🚀 MCP Protocol Super-Powers * **Live Progress Reporting (`notifications/progress`):** Real-time percentage encoding updates streamed directly to modern MCP clients (Claude Desktop, Cursor, Antigravity). * **Instant Cancellation (`AbortSignal`):** Child FFmpeg processes are cleanly terminated (`SIGTERM`/`SIGKILL`) immediately when a user cancels in their client. * **Timeout & Deadlock Protection:** Guard against hanging processes on corrupted or network streams. #### ⚡ Universal Hardware Acceleration * Automatically detects and utilizes GPU encoders across all major operating systems: * **macOS (Apple Silicon):** `h264_videotoolbox`, `hevc_videotoolbox` * **NVIDIA GPUs (Linux/Windows):** `h264_nvenc`, `hevc_nvenc` * **Intel QuickSync:** `h264_qsv`, `hevc_qsv` * **AMD Radeon:** `h264_amf`, `hevc_amf` * **Linux VA-API:** `h264_vaapi`, `hevc_vaapi` * Runtime capability validation ensures smooth fallback to software if drivers are absent. #### 🛠️ 4 New Production Tools (17 Tools Total) * **`burn_subtitles`**: Hardcodes subtitles directly onto video frames with customizable font size, colors, outline, and positioning for TikTok, Reels, and Shorts. * **`extract_keyframes`**: Extracts representative frames across the video and generates a contact sheet grid image with inlined base64 previews for multimodal vision models. * **`normalize_audio`**: Broadcast-standard EBU R128 loudness normalization (-16 LUFS for podcasts/shorts, -14 LUFS for YouTube) with optional speech clarity filtering. * **`add_overlay`**: Watermark and logo overlay with customizable corner positioning, padding, scale, and opacity. #### 📦 MCP Resources & Prompts * **Resources:** `media://capabilities` (FFmpeg hardware info) & `media://presets` (social media aspect ratios & size targets). * **Prompts:** `social_clip_generator` & `whisper_audio_prep`. #### 🐛 Fixes & Improvements * Fixed video A/V lip-sync issue in silence trimming by applying synchronized cuts. * Modularized Zod schemas and expanded automated test suite to 19 passing suites.
Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24; release notes from the GitHub Releases API, checked 2026-10-24.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package @ash_j1997/ffmpeg-mcp-server
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"ffmpeg-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ash_j1997/ffmpeg-mcp-server@0.5.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ffmpeg-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ash_j1997/ffmpeg-mcp-server@0.5.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"ffmpeg-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ash_j1997/ffmpeg-mcp-server@0.5.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"ffmpeg-mcp-server","type":"stdio","command":"npx","args":["-y","@ash_j1997/ffmpeg-mcp-server@0.5.0"]}'Claude Code
claude mcp add --transport stdio ffmpeg-mcp-server -- npx -y @ash_j1997/ffmpeg-mcp-server@0.5.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @ash_j1997/ffmpeg-mcp-server@0.5.0
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.5.0
- Latest stable
- 0.5.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-24. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-24 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-fq/VTWu6w0etXx4Bj…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-10-24.
Usage
- Downloads
- 402 in the last month
Source: api.npmjs.org · 2026-10-24.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.5.0 on npm | Exists and can be installed | matches | npm · 2026-10-24 |
| Repository github.com/Ashutos1997/ffmpeg-mcp-server | Opens publicly | matches | api.github.com · 2026-10-24 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.Ashutos1997
- GitHub owner
- a personal account (Ashutos1997)
- Build record
- signed
- Repository
- github.com/Ashutos1997/ffmpeg-mcp-server
- Stars
- 2
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-24; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- Not ranked by downloads: no download figure available
- Not ranked by stars: 2 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.Ashutos1997/ffmpeg-mcp-server
Answered from the data aboveIs io.github.Ashutos1997/ffmpeg-mcp-server safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.Ashutos1997/ffmpeg-mcp-server been security tested?
Not yet. It could be started, but has not been tested yet. This is our limit, not the server's.
Does io.github.Ashutos1997/ffmpeg-mcp-server publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.5.0, the latest stable release on npm.
Where is the source code of io.github.Ashutos1997/ffmpeg-mcp-server?
In github.com/Ashutos1997/ffmpeg-mcp-server, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.IncorporatedPartners/labelhead-artist-momentumcompare with this one
- io.github.tldraw/tldrawcompare with this one
- io.github.DayuanJiang/next-ai-drawioNext AI Draw.iocompare with this one
- io.github.modelscope/funasr-mcpFunASRcompare with this one
- io.github.BuilderIO/agent-native-assetsAgent-Native Assetscompare with this one
- io.github.BuilderIO/agent-native-designAgent-Native Designcompare with this one
Active servers whose topic is also “media-and-design”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested yet. This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.Ashutos1997/ffmpeg-mcp-server: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.github.Ashutos1997/ffmpeg-mcp-server
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.Ashutos1997/ffmpeg-mcp-server)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology