Golden Hour Selector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LASTFM_USER | No | Your Last.fm username, used to fill my_plays from your scrobbles. | |
| LASTFM_API_KEY | No | Your free Last.fm API key. | |
| SPOTIFY_CLIENT_ID | Yes | Your Spotify developer app Client ID. | |
| SPOTIFY_EXPORT_DIR | No | Default export folder for exported playlist CSV files. | |
| SPOTIFY_TOKEN_PATH | No | Override where the Spotify token is stored. Defaults to ~/.ai/mcp-spotify/spotify.json. | |
| MUSICBRAINZ_CONTACT | No | A URL or address of yours to identify your client to MusicBrainz. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playA | Search Spotify for a track by name and start playing it. Plays on the active device, or on a named device (e.g. a Sonos room) when 'device' is given. Returns the now_playing state. |
| pause_resumeA | Pause, resume, or toggle Spotify playback on the active device. Returns the now_playing state. |
| skipA | Skip to the next or previous track on the active Spotify device. Returns the now_playing state. |
| now_playingA | Get the current Spotify playback state: track, artist, album, device, progress, and volume. |
| volumeA | Set Spotify volume on the active device: absolute level (0-100) or relative delta. Returns now_playing. |
| play_moodA | Play music matching a mood (e.g. focus, chill, energetic, happy). Plays on the active device, or on a named device (e.g. a Sonos room) when 'device' is given. Falls back to search on an unknown mood. |
| launch_appA | Launch the local Spotify desktop app so it becomes a controllable device, then wait briefly and report available devices. Use when no active device is available before playing. |
| list_devicesA | List the available Spotify Connect devices (id, name, type, is_active, volume_pct). Use to discover device names — e.g. linked Sonos rooms — before playing or transferring to one. |
| transferA | Move playback to a Spotify Connect device by name (case-insensitive partial match, e.g. a Sonos room like 'kitchen'). Returns now_playing. |
| searchA | Search Spotify for tracks by name and return the top matches with their spotify: URIs. Does NOT play — use to resolve a song name to a URI (e.g. to then play it on a Sonos room via mcp-sonos). |
| list_playlistsA | List the user's Spotify playlists (owned and followed) with id, owner, track count and whether their tracks are readable (owned or collaborative). |
| playlist_tracksA | List the tracks of one playlist (by name, id, spotify: URI or open.spotify.com URL). Only playlists the user owns or collaborates on are readable. |
| export_playlistsA | Export all readable playlists (plus Liked Songs) to CSV files enriched with album, year, ISRC, genres and, where Spotify still allows, tempo/key. Writes tracks.csv + playlists.csv and returns their paths and a summary. Can take minutes for large libraries. |
| create_playlistB | Create a new playlist in the user's account (private by default). Returns its id and URL. |
| add_to_playlistA | Add tracks to a playlist the user owns or collaborates on, by spotify:track: URIs (resolve names first with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools target a distinct action+resource: search resolves names, play starts playback, play_mood plays by mood, add_to_playlist vs create_playlist are clearly separated. The main overlap is play vs play_mood (both start playback, one by track name and one by mood), but the descriptions make the boundary reasonably clear.
There is a readable verb_noun core (add_to_playlist, play_mood, launch_app, list_devices, list_playlists, create_playlist, export_playlists), but it is mixed with bare verbs and nouns (play, skip, search, transfer, volume, now_playing, pause_resume). The conventions are inconsistent, though each name is still understandable.
15 tools is at the top of the well-scoped range but each one covers a distinct capability: playback control, device management, search, and playlist read/write/export. Nothing feels redundant or padded for a Spotify control server.
Core workflows (search, play, device transfer, playlist listing/creation/export) are covered, but there are notable gaps: no remove-from-playlist or delete-playlist, no queue management, no seek/shuffle/repeat, and no save/like track. These omissions will force agents to work around common playlist-editing and playback-control tasks.