| 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