io.github.AceDataCloud/mcp-minimax vs FFmpeg MCP Server
io.github.AceDataCloud/mcp-minimax is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). FFmpeg MCP Server is an MCP server published by Ashutos1997. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2026.10.18.4 Downloads/month (PyPI): 2 470 Downloads/week (PyPI): 607 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.5.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 2026.10.18.4 Downloads/month (PyPI): 2 470 Downloads/week (PyPI): 607 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.AceDataCloud/mcp-minimax | FFmpeg MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-19 (worse) | 2026-10-23 (better) |
| Where it runs (differs) | Remote server or your machine | On your machine (@ash_j1997/ffmpeg-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/acedatacloud/minimaxmcp | github.com/ashutos1997/ffmpeg-mcp-server |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-22 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.AceDataCloud/mcp-minimax
MCP server for MiniMax H3 multimodal video generation
FFmpeg MCP Server
FFmpeg & FFprobe media processing toolkit for video, audio, and social formats
How to run each
io.github.AceDataCloud/mcp-minimax As a remote MCP server
claude mcp add --transport http mcp-minimax https://minimax.mcp.acedata.cloud/mcp
Requires: ACEDATACLOUD_API_TOKEN (secret)
FFmpeg MCP Server As a local MCP server: npm package
claude mcp add --transport stdio ffmpeg-mcp-server -- npx -y @ash_j1997/ffmpeg-mcp-server
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.AceDataCloud/mcp-minimax has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of FFmpeg MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: io.github.AceDataCloud/mcp-minimax · What it can do: FFmpeg MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.