Available tools
The MCP server exposes 17 tools across 5 areas. Tools that read public catalog data work without authentication. Tools that touch a user's library require the OAuth flow from Quickstart.
Six of the track-returning tools render an inline track player with cover art, play/pause, BPM, and tags. Marked with UI below.
Search and discovery
| Tool | What it does | Auth |
|---|---|---|
search_tracks | Natural-language search via Slipstream's AI ranking. UI | Public |
search_similar_by_url | Find tracks similar to a YouTube, Spotify, or Apple Music URL. UI | Public |
search_by_id | Find tracks similar to a Slipstream track ID. UI | Public |
get_search_filters | List valid genres, moods, tempos, vocals, BPM ranges. | Public |
Catalog
| Tool | What it does | Auth |
|---|---|---|
get_track | Full details for one track by ID. UI | Public |
browse_tracks | Catalog browse with genre and mood filters, paginated. UI | Public |
list_genres | All genres with slugs and descriptions. | Public |
list_moods | All moods with slugs and descriptions. | Public |
Playlists (public)
| Tool | What it does | Auth |
|---|---|---|
search_playlists | Search public playlists by name, description, or tracks. | Public |
get_playlist_tracks | List tracks in a playlist. Pass public=true to read a public one. UI | Public if public=true, otherwise OAuth |
User and library
| Tool | What it does | Auth |
|---|---|---|
get_current_user | The signed-in user's profile. | OAuth |
get_liked_tracks | The user's liked tracks. | OAuth |
Playlists (private)
| Tool | What it does | Auth |
|---|---|---|
list_my_playlists | Playlists owned by the user. | OAuth |
create_playlist | Create a new playlist, optionally with tracks. | OAuth |
get_playlist | Playlist details by slug. | OAuth |
add_tracks_to_playlist | Add tracks to an existing playlist. | OAuth |
delete_playlist | Delete a playlist by slug. | OAuth |
Notes
- Every tool is a thin wrapper around the Slipstream REST API. When the catalog improves, MCP gets the same improvement at the same time.
- Tool inputs and outputs are typed. Most clients show the full schema in their settings UI when you click a tool.
- The track player respects your client's theme. Light and dark both work without configuration.