lyricmood-mcp
Related Servers
Alternatives to lyricmood-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceBridges multiple lyrics providers (LRCLIB, Genius, Musixmatch, Melon) into a single toolchain accessible via MCP, HTTP, or CLI.30 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for Spotify control and synchronized lyrics retrieval that enables playback management, queue navigation, and music search capabilities. It also features perception tools for real-time track analysis, including BPM, key detection, and timestamped lyrics.3Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that enables searching tracks and fetching lyrics, including time-synced LRC lyrics, from LRCLIB without requiring an API key.3158 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides Last.fm listening analytics and recommendations by combining Last.fm and MusicBrainz metadata, maintaining a local listening index, and recording explicit preferences. Enables queries for listening summaries, taste profiles, artist context, and evidence-backed recommendations via MCP tools.67 npmMIT
- AlicenseAqualityBmaintenanceMCP server for lyrics.com that enables searching songs by lyrics or title and retrieving full lyrics, with no API key required.396 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search Spotify's track catalog and retrieve the connected user's recently played tracks through natural language tool calls.127 npmMIT
TDQS
Scored across 14 tools
Most tools target distinct resource+action pairs, and the potentially confusing trio (get_lyrics vs get_track_profile vs now_playing) is explicitly disambiguated in the descriptions (plain lyrics vs full profile vs currently playing). The propose-vs-save split between build_mood_playlist and create_spotify_playlist is also clean. Only minor residual overlap remains, so an agent rarely misselects.
Names follow a consistent snake_case verb_noun pattern (get_*, create_*, update_*, build_*, find_*, search_*, analyze_*). The lone deviation is `now_playing`, which is a state noun rather than a verb_noun action. The convention is otherwise very predictable.
Fourteen tools sit comfortably in the well-scoped 3-15 range, and each one maps to a distinct capability (library reads, discovery, lyrics analysis, playlist writing). No tool feels redundant or padded.
The surface covers the core lifecycle: search/profile/lyrics, discovery via similar-by-lyrics and mood playlists, reading the user library, and creating/updating playlists. Gaps include no playlist deletion or unfollow and no dedicated album/artist-profile lookup, but agents can work around these for the stated lyric+mood purpose.