Ffmpeg Micro MCP vs Vidin
A side-by-side look at the Ffmpeg Micro MCP and Vidin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ffmpeg Micro MCP for multimedia process work as a local process; choose Vidin for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ffmpeg Micro MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FFMPEG_MICRO_API_KEY.
Choose Vidin when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 44/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FFMPEG_MICRO_API_KEY | None listed |
| Verified owner |
Tools & capabilities
Ffmpeg Micro MCP tools
No tool names declared yet. Check the project README from the listing page.
Vidin tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ffmpeg Micro MCP
{
"mcpServers": {
"mcp-server-26": {
"command": "npx",
"args": [
"-y",
"@ffmpeg-micro/mcp-server"
],
"env": {
"FFMPEG_MICRO_API_KEY": "YOUR_FFMPEG_MICRO_API_KEY_HERE"
}
}
}
}
Vidin
{
"mcpServers": {
"vidin": {
"command": "npx",
"args": [
"-y",
"@teunlao/vidin"
]
}
}
}
Frequently asked questions
Ffmpeg Micro MCP is categorized under Multimedia Process and uses a local stdio subprocess. Vidin belongs to Multimedia Process and uses a local stdio subprocess. Pick Ffmpeg Micro MCP for multimedia process work and Vidin for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ffmpeg Micro MCP has no declared pricing — check the project's own site. Vidin has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-server-26 and vidin as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ffmpeg Micro MCP has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Vidin has 41/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.