Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vibrai.com/llms.txt

Use this file to discover all available pages before exploring further.

Create, rename, list, and delete tracks.

Command line

track list

List all tracks
vibrai track list

track get

Get track by ID
vibrai track get <track>
track
required
Track number (1-based: 1, 2, … or first, second, …)

track create

Create a new track
vibrai track create <name> --type <PARTTYPE>
name
required
Track name
--type
default:"Other"
Part type (Bass, Lead, Melody, etc.)

track delete

Delete a track by its ID
vibrai track delete [track] --liveset-id <ID>
track
Positional track number (1-based: 1, 2, … or first, second, …). Omit if using —liveset-id.
--liveset-id
Stable liveset_id from vibrai track list --json; preferred over the positional track number when available (survives reorders).

track rename

Rename a track by its ID
vibrai track rename [track] [name] --liveset-id <ID>
track
Positional track number (1-based: 1, 2, … or first, second, …). Omit if using —liveset-id (in that case pass <name> alone after the flag).
name
New track name. Required (validated at runtime; declared optional only so Spectre permits the —liveset-id <name> shape).
--liveset-id
Stable liveset_id from vibrai track list --json; preferred over the positional track number when available (survives reorders).

MCP tools

list_tracks

List all tracks in the current Live set. Track id is 1-based. midi_index is the ordinal among MIDI tracks only (also 1-based), or null for audio tracks.
{
  "tool": "list_tracks",
  "arguments": {}
}

create_track

Create a new MIDI track of the given part type.
{
  "tool": "create_track",
  "arguments": {
    "name": "<String>",
    "type": "<PartType>"
  }
}
name
String
required
Track display name
type
PartType
required
Part type (drums, bass, chords, lead, pad, fx, etc.)

delete_track

Delete a track. Pass either track_id (positional, 1-based) or liveset_id (stable across reorders — get it from list_tracks). liveset_id wins if both are supplied. Subsequent tracks shift down so positional IDs stay dense; existing liveset_ids on the remaining tracks are unaffected. Destructive — no undo.
{
  "tool": "delete_track",
  "arguments": {
    "track_id": "<String>",
    "liveset_id": "<String>"
  }
}
track_id
String
required
Positional track number (1-based: 1, 2, … or ‘first’, ‘second’, …)
liveset_id
String
required
Stable liveset_id from list_tracks; preferred over track_id when available.

set_track_name

Rename a track. Pass either track_id (positional, 1-based, may shift on reorder) or liveset_id (stable across reorders within one Live session — get it from list_tracks). liveset_id wins if both are supplied. Use liveset_id when you plan to issue multiple ops on the same track over time, especially across track insertions.
{
  "tool": "set_track_name",
  "arguments": {
    "track_id": "<String>",
    "liveset_id": "<String>",
    "name": "<String>"
  }
}
track_id
String
required
Positional track number (1-based: 1, 2, … or ‘first’, ‘second’, …)
liveset_id
String
required
Stable liveset_id from list_tracks; preferred over track_id when available.
name
String
required
New track name