music-digger-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUSIC_DIARY_SUBDIR | No | Subdirectory for music diary entries | music/diary |
| MUSIC_ALBUMS_SUBDIR | No | Subdirectory for album cards | music/albums |
| OBSIDIAN_VAULT_PATH | Yes | Your Obsidian Vault path (required) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| current_trackA | Return the currently playing track info, based on what this MCP last started. Reflects MCP-driven playback only; manual browser interaction is not tracked. |
| play_albumA | Play an album by artist + album name. Searches YouTube for |
| play_stationA | Start a YouTube station from an artist or genre seed. Opens the top result in Safari. When seed is omitted, picks one at random from the Obsidian stations note (MUSIC_STATIONS_PATH). |
| mark_currentA | Stamp the currently playing track with a reaction (love/like/meh/skip). Appends to the day diary and promotes to an album card on love>=1 or like>=2. YouTube title parsing can be overridden with explicit |
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 4 tools
Each tool serves a distinct purpose: displaying current track, reacting, playing album, and playing station. No overlap in functionality.
All names use snake_case and follow a verb_noun pattern except 'current_track' (adjective_noun). Consistency is high with only a minor deviation.
Four tools is well-scoped for a music discovery server. Each tool contributes a necessary function without redundancy.
Core actions (display, react, play album/station) are covered. Missing features like search or basic playback controls (skip, pause) but acceptable for focused scope.