Connect Claude to Vocuno for AI music generation, editing, stem separation, voice conversion, mixing, mastering, and analysis.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Vocuno.
The Vocuno MCP server gives Claude access to Vocuno’s AI music studio through a remote MCP connection. It supports creating complete songs from text prompts or supplied lyrics, with vocals and multiple available music models. Claude can also request covers, stylistic remixes, and mashups involving two tracks.
Music processing extends beyond generation. The server can split tracks into vocals, drums, bass, and other instruments, remove reverb, and extract MIDI from stems. Voice-related operations include changing the voice in vocals and cloning a voice for later generations. Song-level operations include extending a track, replacing a passage, mixing, mastering, identifying BPM and chords, and converting audio formats.
The integration also belongs in the 🎥 Multimedia Process category for workflows that combine generation, transformation, and analysis. Results are stored in the connected Vocuno account, where they appear alongside work created on the website. Responses can include shareable streaming links.
The Vocuno MCP server is hosted remotely at Vocuno and is connected over HTTP. Claude sends requests through MCP, while Vocuno performs the requested generation or audio operation in the user’s account. On the first connection, Claude opens a browser-based sign-in flow using OAuth 2.1. After the user approves access, the connection can be used without manually creating or storing an API key.
Generated content and processed files are associated with the user’s Vocuno library. Account-related operations can report remaining credits and provide the status and shareable links for generations. The service applies the same credit rules as the Vocuno website: generation features use credits, while editing and analysis features identified as free do not.
Install the official plugin from Claude Code with:
Alternatively, register the remote MCP endpoint directly:
A Vocuno account is required. New accounts include free credits, but generation usage consumes the account’s Vocuno credits. The README does not specify environment variables or additional local configuration. Authentication is completed through the browser the first time Claude connects.
The Vocuno MCP server covers these supported areas:
A Vocuno account is necessary, and generation tools consume credits according to Vocuno’s service rules. Free editing and analysis operations do not consume credits when marked free by the service. The plugin package is MIT licensed, but the Vocuno service is governed separately by Vocuno’s Terms of Service. The provided material documents Claude Code installation and does not list support details for other MCP clients.
The Vocuno MCP server depends on the remote Vocuno service, so account access and the service endpoint are required for operation. No local API-key configuration is described in the available documentation.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/vocuno)<a href="https://allmcps.com/mcp/vocuno"><img src="https://allmcps.com/api/badge/vocuno?style=directory" alt="Vocuno on AllMCPs" /></a>