@cassette.diy/mcp
Required for uploads; provides OAuth URL to link Google Drive and enables file uploads to Cassette via Drive.
Allows updating Spotify pitch metadata on Cassette tracks.
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., "@@cassette.diy/mcp create a new track called 'Midnight'"
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.
@cassette.diy/mcp
MCP server for Cassette (music releases) and Cassette for Creators (short-form clips). Lets AI assistants in Cursor, Claude Desktop, and other MCP clients manage your Cassette account via personal access tokens.
npm: https://www.npmjs.com/package/@cassette.diy/mcp
Docs: https://cassette.diy/docs/mcp
Install
Published on npm. No separate install step when using Cursor — npx downloads the package on first run:
npx -y @cassette.diy/mcpA Cassette or Creator account with Google Drive linked (required for uploads).
A personal access token from the web app:
Music app: Settings → API / AI access
Creator app: Settings → API / AI access
Related MCP server: vcon-mcp
Cursor setup
Add to your Cursor MCP config (~/.cursor/mcp.json or project .cursor/mcp.json):
{
"mcpServers": {
"cassette": {
"command": "npx",
"args": ["-y", "@cassette.diy/mcp"],
"env": {
"CASSETTE_API_URL": "https://api.cassette.diy",
"CASSETTE_API_TOKEN": "ct_live_YOUR_TOKEN_HERE",
"CASSETTE_PRODUCT": "both"
}
}
}
}You can copy a ready-made snippet from Settings after creating a token.
Environment variables
Variable | Required | Description |
| No | Backend URL (default: |
| Yes | Personal access token ( |
| No |
|
Local development
From the monorepo:
cd cassette-mcp
npm install
npm run buildPoint Cursor at the local package:
{
"mcpServers": {
"cassette": {
"command": "node",
"args": ["/absolute/path/to/Cassette/cassette-mcp/dist/index.js"],
"env": {
"CASSETTE_API_URL": "http://localhost:8080",
"CASSETTE_API_TOKEN": "ct_live_...",
"CASSETTE_PRODUCT": "both"
}
}
}
}Tool catalog
Set CASSETTE_PRODUCT to music, creator, or both (default: both).
Shared
Tool | Description |
| Profile, Drive link status, tiers |
| OAuth URL to link Google Drive |
| Find users for invites (creator mode only) |
Music — track creation workflow
Focused tools for musicians: create a release end-to-end (no delete, collaboration, or Drive sync).
Tool | Description |
| Create track (name, artist, release date) |
| Upload artwork, audio, promo, footages, vertical videos |
| Metadata, Spotify pitch, notes |
| List uploaded files by category |
| Get full track after creation |
Creators
Full clip workflow (unchanged):
Tool | Description |
| Tier, limits, clip count |
| List clips |
| Clip CRUD |
| Scenario time blocks |
| Freeform notes |
| Trend library |
| New clip from trend |
| Footages |
| Final video & links |
| Collaboration |
Uploads
Upload tools read files from local_path on the machine running the MCP server (your computer when using stdio in Cursor).
< 10 MB — direct multipart upload
10–20 MB — async upload + task polling
> 20 MB (tracks) — chunked upload + task polling
If Drive is not linked, upload tools fail; use cassette_start_gdrive_link first.
Token scopes
Scope | Access |
| GET on |
| Mutations on |
| GET on |
| Mutations on |
Tokens cannot access admin, Stripe checkout, analytics, or token management endpoints.
Publish checklist
Deploy backend with
api_tokenscollection and routesVerify token create/list/revoke in staging Settings UI
Smoke-test MCP tools against staging API
Publish
@cassette.diy/mcpto npm (v0.1.0)Set production
CASSETTE_API_URLin docsOptional: track
mcp_token_createdanalytics event
License
UNLICENSED — internal Cassette package.
Available Tools
28 toolscassette_create_clipC
Create a new creator clip.
Inputs: name (required).
cassette_create_trackB
Create a new music track/release. First step of the track creation workflow.
Inputs: name (required), artist (required), releaseDate, release, +2 more.
cassette_create_trendD
Save a trend video URL.
Inputs: url (required), title, notes.
cassette_delete_clipC
Delete a creator clip.
Inputs: clipId (required).
cassette_delete_footageC
Delete a footage file from a clip.
Inputs: clipId (required), fileId (required).
cassette_delete_trendB
Delete a trend from the library.
Inputs: trendId (required).
cassette_get_accountA
Get Cassette account status: profile, Google Drive link, music/creator tiers, and readiness for uploads.
Inputs: no named parameters.
cassette_get_clipC
Get a creator clip by ID.
Inputs: clipId (required).
cassette_get_creator_billingA
Get Creator subscription tier, limits, and clip count.
Inputs: no named parameters.
cassette_get_finalC
Get final video metadata and post links for a clip.
Inputs: clipId (required).
cassette_get_trackA
Get a track by ID with full metadata and file references. Use after creation to verify the workflow.
Inputs: trackId (required).
cassette_list_clipsC
List creator clips.
Inputs: scope.
cassette_list_footagesB
List footages uploaded for a clip.
Inputs: clipId (required).
cassette_list_track_filesB
List uploaded files on a track (audio, promo, footages, verticalVideos, video) to verify uploads.
Inputs: trackId (required), fileType (required).
cassette_list_trendsA
List saved trend videos.
Inputs: no named parameters.
cassette_review_footageC
Update footage review metadata (selected, rating 0-5, note).
Inputs: clipId (required), fileId (required), selected, rating, +1 more.
cassette_search_usersA
Search Cassette users by email (for creator clip collaboration invites).
Inputs: query (required).
cassette_start_clip_from_trendC
Create a new clip from a trend with default scenario template.
Inputs: trendId (required).
cassette_start_gdrive_linkA
Get Google Drive OAuth URL so the user can link Drive (required before file uploads).
Inputs: frontendUrl.
cassette_update_clipA
Update clip fields (name, status, progress, etc.).
Inputs: clipId (required), updates (required).
cassette_update_clip_notesB
Update freeform notes on a clip.
Inputs: clipId (required), notes (required).
cassette_update_post_linksC
Update social post links on the final video.
Inputs: clipId (required), tiktok, instagramReels, youtubeShorts, +1 more.
cassette_update_scenarioC
Update scenario time blocks for a clip.
Inputs: clipId (required), scenario (required).
cassette_update_track_metadataA
Update track fields via PATCH /metadata (same fields as the Cassette app): pitchEn, pitchNative, notes, status, progress, multilink, name, artist, release, releaseDate, isSingle.
Inputs: trackId (required), pitchEn, pitchNative, notes, +8 more.
cassette_upload_finalC
Upload final video for a clip from a local path.
Inputs: clipId (required), localPath (required), replace.
cassette_upload_footageC
Upload a footage file to a clip from a local path.
Inputs: clipId (required), localPath (required).
cassette_upload_track_fileC
Upload artwork, audio, promo images, footages, or vertical videos from a local path. Requires Google Drive linked.
Inputs: trackId (required), fileType (required), localPath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
Each tool targets a distinct resource and action (e.g., clips, tracks, footages, trends). Overlaps like cassette_create_clip vs cassette_start_clip_from_trend are clearly differentiated by context. All tools have clear, non-overlapping purposes.
All tools follow a consistent 'cassette_verb_noun' pattern in snake_case. Verbs like create, delete, get, list, update are used predictably. No mixing of conventions or vague names.
28 tools is slightly above the recommended range for a typical server. While each tool earns its place given the domain's complexity, the count feels heavy and could potentially be consolidated (e.g., merging manage_clip_shares into separate tools).
The tool surface covers core workflows for clips, tracks, footages, trends, and account management. Minor gaps exist, such as missing delete_track and list_tracks tools, but these are not critical and can be worked around.
Maintenance
Related MCP Connectors
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Remote MCP server for AI.TV creators — delegate account operations to your AI agent over MCP.
MCP server for Producer/Riffusion AI music generation
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.21117 PyPI2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for storing, managing, and analyzing IETF vCon (Virtual Conversation) data with AI assistants.26 npm4MIT
- FlicenseAqualityDmaintenanceA lightweight MCP server that enables AI assistants like Cursor and Claude to control Spotify playback, playlists, and manage tokens via OAuth.152-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that enables AI assistants to control music playback, manage users and access, configure providers, and administer a Music Assistant setup through natural language commands.MIT