FFMPEG API vs Tuney
A side-by-side look at the FFMPEG API and Tuney MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TuneyMultimedia ProcessRoyalty-free music fitted to your length: find, generate, adjust and download tracks and stems.36FairAuth: oauth 2.0Verdict: choose FFMPEG API for multimedia process work over a hosted endpoint; choose Tuney for multimedia process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose FFMPEG API when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
TChoose Tuney when
- You need dedicated capabilities in the Multimedia Process domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tuney | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 35/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
FFMPEG API tools
No tool names declared yet. Check the project README from the listing page.
Tuney 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 API
{
"mcpServers": {
"ffmpeg-api-3": {
"url": "https://mcp.ffmpegapi.net/mcp"
}
}
}
Tuney
No confirmed install command for Tuney yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
FFMPEG API is categorized under Multimedia Process and uses a remote HTTP/SSE transport. Tuney belongs to Multimedia Process and uses an install path we have not confirmed yet. Pick FFMPEG API for multimedia process work and Tuney 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. Tuney has no confirmed install command yet — follow its own setup instructions.
FFMPEG API has no declared pricing — check the project's own site. Tuney is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 ffmpeg-api-3 and tuney as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FFMPEG API has a quality signal of 35/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Tuney has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
