mcp-svstudio
The mcp-svstudio server enables integration of Synthesizer V Studio with LLMs for creating and editing vocal tracks.
Key capabilities:
Get project information about the current Synthesizer V Studio project
List all tracks in the project
Retrieve notes from a specific track
Add new tracks to the project
Add notes to a track, specifying lyrics, pitch, duration, and start time
Edit existing notes, modifying lyrics, timing, and pitch
Hosts the repository for the MCP server code, allowing users to clone and install the integration.
Uses Lua scripts to handle communication between the MCP server and Synthesizer V Studio application.
Supports integration with Synthesizer V Studio on macOS, with specific installation paths and configuration requirements.
Provides the runtime environment for the MCP server, enabling communication between LLMs and Synthesizer V Studio.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-svstudio add lyrics to this melody track"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Synthesizer V Studio MCP Server
MCP server for Synthesizer V AI Vocal Studio, which allows LLMs to create/edit vocal tracks e.g. adding lyrics to the melody.
Installation
Prerequisites
Node.js (tested with v22)
Synthesizer V Studio (tested with V2)
0. Clone this repo
git clone https://github.com/ocadaruma/mcp-svstudio.git
1. Configure Synthesizer V Studio
Copy below two files to Synthesizer V Studio scripts folder (On MacOS with V2 Studio, it's
~/Library/Application Support/Dreamtonics/Synthesizer V Studio 2/scriptsby default)sv-scripts/StartMCPServerRequestHandler.luasv-scripts/StopMCPServerRequestHandler.lua
Run
StartServerRequestHandleron Synthesizer V StudioFrom Scripts menu > MCP > StartServerRequestHandler
⚠️ Please do this before configuring MCP client. Otherwise, you will get connection issue.
2. Configure MCP client
⚠️ Please run only one MCP server at a time.
Add below config to the MCP server config of your client. (e.g. On MacOS Claude Desktop, it's ~/Library/Application Support/Claude/claude_desktop_config.json by default)
{
"mcpServers": {
"SynthesizerVStudioMCP": {
"command": "/path/to/node",
"args": [
"/path/to/mcp-svstudio/dist/index.js"
]
}
}
}Related MCP server: SV1 Agent Bridge
Example commands
Sing something (then "Add harmony track")
Create an EDM vocal track
Add lyrics to the existing track
Development
Install dependencies:
npm installBuild the server:
npm run buildFor development with auto-rebuild:
npm run watchAvailable Tools
6 toolsadd_notesC
Add one or more notes to a track
Inputs: trackId (required), notes (required).
add_trackC
Add a new track to the project
Inputs: name.
edit_notesC
Edit one or more notes
Inputs: trackId (required), notes (required).
get_project_infoB
Get information about the current Synthesizer V Studio project
Inputs: no named parameters.
get_track_notesC
Get all notes in a specific track
Inputs: trackId (required).
list_tracksB
List all tracks in the current project
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting specific resources and actions: adding notes, adding tracks, editing notes, getting project info, getting track notes, and listing tracks. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern (e.g., add_notes, add_track, edit_notes, get_project_info, get_track_notes, list_tracks). The naming is uniform and predictable throughout the set.
With 6 tools, the server is well-scoped for managing a Synthesizer V Studio project. Each tool earns its place by covering essential operations like project info, track management, and note handling without being overly sparse or bloated.
The tool set provides strong coverage for core project and track operations, including CRUD-like actions for notes and tracks. A minor gap exists in the lack of tools for deleting notes or tracks, which agents might need to work around, but the surface supports basic workflows effectively.
Related MCP Connectors
MCP server for Producer/Riffusion AI music generation
MCP server for Google Veo AI video generation
MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects AI assistants to FL Studio for music production via Virtual MIDI. It enables users to control transport, manage the mixer, write notes, and manipulate plugin parameters through natural language.1MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that enables AI agents to control Synthesizer V Studio 1.x via its Lua scripting API.3-
- AlicenseAqualityCmaintenanceAn MCP server for Synthesizer V Studio 2 Pro on macOS that enables AI-driven composition and lyric input, including melody creation, lyric flowing, and phoneme tuning.16MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that turns PreSonus Studio One into an AI-controllable DAW, enabling production workflows like editing, MIDI manipulation, mixing, effects, and export through an LLM.12MIT