Sequencer vs Vidofy
A side-by-side look at the Sequencer and Vidofy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SequencerMultimedia ProcessCreate AI images, video, and audio, quote generation costs, and edit Sequencer projects.36FairAuth: oauth 2.0Verdict: choose Sequencer for multimedia process work; choose Vidofy 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?
SChoose Sequencer when
- You need dedicated capabilities in the Multimedia Process domain.
- Its auth model fits you: OAuth 2.0.
Choose Vidofy when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VIDOFY_TOKEN, VIDOFY_API_BASE. - You want tools like
list_modes, list_models, get_model.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Sequencer | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 36/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | VIDOFY_TOKENVIDOFY_API_BASE |
| Verified owner |
Tools & capabilities
Sequencer tools
No tool names declared yet. Check the project README from the listing page.
Vidofy tools 9
list_modesWhat Vidofy can generate: text-to-image, image-to-video, lipsync, speech…list_modelsThe models in one mode, with each one's credit cost and rough durationget_modelOne model's full input contract: a JSON Schema, its file slots and their limitsestimate_costWhat a generation will cost, before running itgenerateRuns it. The only tool that spends the balance.get_statusWhether a generation has finishedget_resultThe finished mediaget_balanceCoins left, and how many expire with the subscriptionget_usageRecent generations and what they cost
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.
Sequencer
No confirmed install command for Sequencer yet — follow the setup steps linked from its listing page rather than a guessed package name.
Vidofy
{
"mcpServers": {
"vidofy": {
"command": "npx",
"args": [
"-y",
"@vidofy/mcp"
],
"env": {
"VIDOFY_TOKEN": "YOUR_VIDOFY_TOKEN_HERE",
"VIDOFY_API_BASE": "YOUR_VIDOFY_API_BASE_HERE"
}
}
}
}
Frequently asked questions
Sequencer is categorized under Multimedia Process and uses an install path we have not confirmed yet. Vidofy belongs to Multimedia Process and uses a local stdio subprocess. Pick Sequencer for multimedia process work and Vidofy 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. Sequencer has no confirmed install command yet — follow its own setup instructions.
Sequencer has no declared pricing — check the project's own site. Auth: oauth 2.0. Vidofy 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 sequencer and vidofy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sequencer has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Vidofy has 57/100 (Good) with 0 views, 0 installs and 2 GitHub stars.