mcp-svstudio
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_infoB | Get information about the current Synthesizer V Studio project |
| list_tracksB | List all tracks in the current project |
| get_track_notesC | Get all notes in a specific track |
| add_notesC | Add one or more notes to a track |
| add_trackC | Add a new track to the project |
| edit_notesC | Edit one or more notes |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.