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.
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_soundcloudA | Log in to SoundCloud: opens a browser for OAuth and stores the token for future sessions |
| auth_statusA | Check whether a SoundCloud user is logged in |
| sign_outA | Sign out and forget the stored SoundCloud token |
| search_tracksC | Search for tracks with optional filters |
| search_playlistsB | Search for playlists by keyword |
| search_usersC | Search for users by keyword |
| get_trackA | Get information about a specific track |
| get_userB | Get a user's public profile by ID |
| get_playlistC | Get information about a specific playlist |
| get_related_tracksC | Get tracks related to a specific track |
| get_stream_urlA | Get playable audio stream URLs for a track (time-limited) |
| get_commentsC | Get comments for a track |
| get_profileB | Get the logged-in user's SoundCloud profile |
| get_likesC | Get the logged-in user's liked tracks |
| get_playlistsB | Get the logged-in user's playlists |
| get_recommended_tracksC | Get personalized track recommendations |
| like_trackC | Like a track |
| unlike_trackD | Unlike a track |
| follow_userC | Follow a user |
| unfollow_userC | Unfollow a user |
| add_commentC | Add a comment to a track |
| create_playlistC | Create a new playlist, optionally with tracks |
| update_playlistA | Rename, redescribe, change sharing, or replace the tracklist of a playlist |
| add_tracks_to_playlistC | Append tracks to an existing playlist |
| remove_track_from_playlistC | Remove a track from a playlist |
| delete_playlistB | Delete a playlist permanently |
| get_conversationsC | Get your direct message conversations |
| get_conversationC | Get details of a specific conversation |
| get_messagesC | Get messages from a conversation |
| send_messageC | Send a message in a conversation |
| start_conversationC | Start a new conversation with a user |
| mark_conversation_readB | Mark a conversation as read |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_music_taste | Analyze a user's music taste based on their liked tracks |
| discover_similar_tracks | Find tracks similar to a specific track |
| discover_new_music | Get personalized music discovery recommendations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| my-profile | The logged-in user's profile |
| my-playlists | The logged-in user's playlists |
| my-likes | The logged-in user's liked tracks |
TDQS
Scored across 32 tools
Each tool targets a distinct action or resource, with no overlapping purposes. Even similar tools like get_recommended_tracks and get_related_tracks are clearly differentiated by description.
All tool names follow a consistent verb_noun pattern (e.g., follow_user, create_playlist, get_track). Minor exceptions like auth_status are still clear and predictable.
With 32 tools, the server exceeds the recommended range for typical MCP servers. While the scope justifies many endpoints, this number may overwhelm agent context windows.
The tool surface covers major SoundCloud operations: authentication, user actions, playlists (CRUD plus track management), tracks (search, liking, comments, stream), and messaging. Missing track creation/upload is likely due to API limitations.