Audial vs Vocuno
A side-by-side look at the Audial and Vocuno MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Audial for multimedia process work as a local process; choose Vocuno for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Audial when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
stem_split, analyze, segment.
Choose Vocuno when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 75/100 · Great | 74/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Verified |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 41 views 0 installs 0 upvotes |
| Tools | 10 | Not listed |
| Full listing | View Audial | View Vocuno |
Tools & capabilities
Audial tools 10
stem_splitSplit a track into vocals, drums, bass, other (optionally retime / rekey)analyzeBPM, key and other characteristicssegmentSections and component analysismasterMastering, optionally matched to a referencegenerate_samplesSample pack from a trackgenerate_midiAudio to MIDIgenerate_musicText to music, covers, remixes, extraction, completion with the Audial music modelsound2vitalOne-shot → editable Audial Synth (Vital) presettext2voxLyrics + reference voice → sung vocal and MIDIlist_resultsBrowse previous results in your results folder
Vocuno 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.
Audial
{
"mcpServers": {
"audial": {
"command": "uvx",
"args": [
"audial-mcp"
]
}
}
}
Vocuno
{
"mcpServers": {
"vocuno": {
"url": "https://vocuno.com/mcp"
}
}
}
Frequently asked questions
Audial is categorized under Multimedia Process and uses a local stdio subprocess. Vocuno belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Audial for multimedia process work and Vocuno 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.
Audial has no declared pricing — check the project's own site. Vocuno 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 audial and vocuno as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Audial has a quality signal of 75/100 (Great) with 0 views, 0 installs and 0 GitHub stars. Vocuno has 74/100 (Great) with 41 views, 0 installs and 1 GitHub stars.