SoundCloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DEBUG | No | Set true for verbose request logging to stderr | |
| SOUNDCLOUD_CLIENT_ID | Yes | App client ID | |
| SOUNDCLOUD_TOKEN_FILE | No | Token storage path (default ~/.soundcloud-mcp/tokens.json) | |
| SOUNDCLOUD_REDIRECT_URI | Yes | Must match the app's redirect URI exactly (default http://localhost:8888/callback) | |
| SOUNDCLOUD_CLIENT_SECRET | Yes | App client secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
SoundCloud, through the official API.
Resolve pasted SoundCloud links with
resolve_url.Prefer URNs (
soundcloud:tracks:123); numeric ids also work.Pass
next_hreftonext_page. Page size: 50 by default, 200 max.Public search needs no login. Use
connect_soundcloudfor personal data and writes.For recommendations, use
get_related_trackswith a liked track or readget_feed.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tracksB | Search SoundCloud tracks by keyword, with optional genre/tag/BPM filters. |
| search_playlistsC | Search SoundCloud playlists by keyword. |
| search_usersC | Search SoundCloud users/artists by keyword. |
| resolve_urlA | Resolve a soundcloud.com or on.soundcloud.com link to a track, user, playlist, or station. Use for pasted SoundCloud links; pass station URNs to get_station. |
| get_trackC | Get details for one track. |
| get_userC | Get a user's public profile. |
| get_user_tracksA | List a user's uploads. Find ids with search_users. Sort: asc for oldest first, desc for newest. |
| get_user_playlistsC | List the playlists a user has published. |
| get_user_likesC | List tracks, playlists, or stations a user has liked. |
| get_user_repostsC | List tracks or playlists a user has reposted. |
| get_user_followersC | List the users who follow a user. |
| get_user_followingsC | List the users a user follows. |
| get_user_web_profilesB | List the external links on a user's profile, such as a website or socials. |
| get_playlistC | Get a playlist's details and its tracks. |
| get_stationA | Get a station (system playlist) and its tracks. Tracks and users carry a station_urn; get_my_likes with kind=stations lists liked ones. |
| get_playlist_tracksC | List a page of playlist tracks. |
| get_playlist_repostersC | List the users who reposted a playlist. |
| get_related_tracksC | Find related tracks, starting with a track the user likes. |
| get_related_artistsC | Find artists related to a user. |
| get_stream_urlA | Get temporary audio URLs: HLS for full tracks, MP3 for previews. Blocked tracks have no stream. |
| get_commentsB | Get comments on a track, with their timestamps into the audio. |
| get_track_likersB | List the users who liked a track. |
| get_track_repostersC | List the users who reposted a track. |
| next_pageA | Fetch next_href with a GET to the SoundCloud API (https://developers.soundcloud.com/docs/api/guide). |
| get_profileB | Get the connected user's SoundCloud profile. |
| get_my_likesB | List tracks, playlists, or stations the connected user has liked. |
| get_my_repostsB | List tracks or playlists the connected user has reposted. |
| get_my_playlistsB | List the connected user's playlists. |
| get_my_tracksB | List the connected user's uploads. Sort: asc for oldest first, desc for newest. |
| get_my_followingsC | List the users the connected user follows. |
| get_my_followersB | List the users who follow the connected user. |
| is_followingA | Check whether the connected user follows a user. Unknown users count as not followed. |
| get_feedA | List recent activity from people the connected user follows: tracks by default, or all for playlists too. |
| get_recently_playedB | Tracks the connected user played recently, most recent first. |
| like_trackD | Like a track. |
| unlike_trackC | Remove a like from a track. |
| repost_trackC | Repost a track to the user's followers. |
| unrepost_trackC | Remove a repost of a track. |
| like_playlistC | Like a playlist or a station. |
| unlike_playlistC | Remove a like from a playlist or a station. |
| repost_playlistB | Repost a playlist to the user's followers. |
| unrepost_playlistC | Remove a repost of a playlist. |
| follow_userC | Follow a user. |
| unfollow_userC | Unfollow a user. |
| add_commentA | Post a comment with an optional timestamp. Comments must be enabled; the API has no undo. |
| create_playlistA | Create a playlist with optional tracks. Private by default. |
| update_playlistA | Edit a playlist's title, description, or sharing. trackIds replaces and orders the entire tracklist. |
| add_tracks_to_playlistC | Append tracks to an existing playlist. |
| remove_track_from_playlistC | Remove one track from a playlist. |
| delete_playlistB | Delete a playlist permanently. |
| connect_soundcloudA | Log in through your browser and save the token for future sessions. |
| auth_statusA | Check whether a SoundCloud user is logged in. |
| sign_outA | Revoke this app's SoundCloud access and delete the stored token. Public search still works afterward. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_music_taste | Analyze the connected user's taste from their liked tracks |
| discover_similar_tracks | Find tracks similar to one you like |
| discover_new_music | Find music based on your likes, genres, and mood |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| my-profile | The connected user's profile |
| my-playlists | The connected user's playlists |
| my-likes | The connected user's liked tracks |
TDQS
Scored across 53 tools
Tools are largely separable by a clear resource+actor pattern (get_my_likes vs get_user_likes, get_track_likers vs get_track_reposters), and descriptions add helpful boundaries. A few overlaps remain fuzzy, notably get_playlist (returns tracks) vs get_playlist_tracks, and the generic next_page which could apply to any listing tool.
The dominant convention is consistent snake_case verb_noun (search_tracks, like_playlist, get_user_followers), applied across virtually all tools. Minor deviations (is_following, auth_status, resolve_url, next_page) are readable predicates but break the strict verb_noun pattern.
53 tools is well above a comfortable surface for a single agent to select from reliably. Much of the bloat comes from parallel families (my_* mirroring user_*, separate like/unlike/repost/unrepost pairs for tracks and playlists) that could be collapsed with parameters.
Coverage is broad: search, detail fetches, likes/reposts/follows, playlist create/update/delete, comments, stations, streaming URLs, and auth lifecycle are all present. Gaps are minor: no comment editing or deletion, and no track upload/delete (largely an API limitation).