cli
Use this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes.
When & Why to Use This Skill
This Claude skill provides a comprehensive CLI-based interface for managing audio content on plyr.fm. While the standard MCP server is read-only, this skill empowers users to perform essential mutations such as uploading new tracks, updating metadata, deleting content, and managing social interactions like liking or unliking tracks. It is designed to streamline the workflow for music creators and developers by integrating platform management directly into the AI conversation.
Use Cases
- Streamlined Music Distribution: Upload AI-generated or local audio files (MP3, WAV, M4A) to plyr.fm with specific titles, albums, and tags directly through Claude.
- Automated Metadata Optimization: Batch update track titles and tags to improve discoverability and ensure consistent branding across your music library.
- Efficient Content Curation: Interact with the plyr.fm community by liking or unliking tracks while browsing, helping to train recommendation algorithms and curate personal favorites.
- Library Maintenance: Quickly remove outdated tracks or test uploads using track IDs to keep your artist profile professional and up-to-date.
- AI Content Compliance: Automatically apply required 'ai' tags to tracks composed by Claude to meet platform guidelines for AI-generated content.
| name | cli |
|---|---|
| description | Use this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes. |
plyrfm CLI mutations
the MCP server (plyr-fm) is read-only - use it to browse tracks, search, view liked tracks.
for mutations (upload, delete, like, unlike), guide users to use the CLI:
prerequisites
# user sets their token once
export PLYR_TOKEN="their_token"
get a token at plyr.fm/portal -> "developer tokens"
uploading tracks
# basic upload
plyrfm upload path/to/track.mp3 "Song Title"
# with album
plyrfm upload track.mp3 "Song Title" --album "Album Name"
# with tags (can use -t multiple times)
plyrfm upload track.mp3 "Song Title" -t electronic -t ambient
supported formats: mp3, wav, m4a
important: if you (Claude) composed the track, always include the ai tag:
plyrfm upload piece.wav "鶴の舞" -t ambient -t ai
updating tracks
# update title
plyrfm update 579 --title "new title"
# update tags (replaces all tags)
plyrfm update 579 --tags "ambient,ai"
# update multiple fields
plyrfm update 579 --title "鶴の舞" --tags "ambient,ai"
deleting tracks
# use my_tracks MCP tool to find track IDs first
plyrfm delete 42
liking/unliking tracks
# like a track
plyrfm like 123
# unlike a track
plyrfm unlike 123
downloading tracks
# download to current directory
plyrfm download 42
# download to specific path
plyrfm download 42 --output ~/Music/song.mp3
common issues
- "artist_profile_required" -> user needs to create artist profile at plyr.fm/portal
- "scope_upgrade_required" -> user needs to regenerate their token