@cassette.diy/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CASSETTE_API_URL | No | Backend URL (default: http://localhost:8080) | http://localhost:8080 |
| CASSETTE_PRODUCT | No | music, creator, or both (default: both) | both |
| CASSETTE_API_TOKEN | Yes | Personal access token (ct_live_…) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cassette_get_accountA | Get Cassette account status: profile, Google Drive link, music/creator tiers, and readiness for uploads. |
| cassette_start_gdrive_linkA | Get Google Drive OAuth URL so the user can link Drive (required before file uploads). |
| cassette_search_usersA | Search Cassette users by email (for creator clip collaboration invites). |
| cassette_create_trackB | Create a new music track/release. First step of the track creation workflow. |
| cassette_upload_track_fileC | Upload artwork, audio, promo images, footages, or vertical videos from a local path. Requires Google Drive linked. |
| 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. |
| cassette_list_track_filesB | List uploaded files on a track (audio, promo, footages, verticalVideos, video) to verify uploads. |
| cassette_get_trackA | Get a track by ID with full metadata and file references. Use after creation to verify the workflow. |
| cassette_get_creator_billingA | Get Creator subscription tier, limits, and clip count. |
| cassette_list_clipsC | List creator clips. |
| cassette_get_clipC | Get a creator clip by ID. |
| cassette_create_clipC | Create a new creator clip. |
| cassette_update_clipA | Update clip fields (name, status, progress, etc.). |
| cassette_delete_clipC | Delete a creator clip. |
| cassette_update_scenarioC | Update scenario time blocks for a clip. |
| cassette_update_clip_notesB | Update freeform notes on a clip. |
| cassette_list_trendsA | List saved trend videos. |
| cassette_create_trendD | Save a trend video URL. |
| cassette_delete_trendB | Delete a trend from the library. |
| cassette_start_clip_from_trendC | Create a new clip from a trend with default scenario template. |
| cassette_list_footagesB | List footages uploaded for a clip. |
| cassette_upload_footageC | Upload a footage file to a clip from a local path. |
| cassette_review_footageC | Update footage review metadata (selected, rating 0-5, note). |
| cassette_delete_footageC | Delete a footage file from a clip. |
| cassette_get_finalC | Get final video metadata and post links for a clip. |
| cassette_upload_finalC | Upload final video for a clip from a local path. |
| cassette_update_post_linksC | Update social post links on the final video. |
| cassette_manage_clip_sharesC | Manage clip collaboration: list, create, invite, accept, revoke, or change role. |
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 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.