mcp-lyricscom
Related Servers
Alternatives to mcp-lyricscom
- AlicenseAqualityBmaintenanceAn MCP server that enables searching tracks and fetching lyrics, including time-synced LRC lyrics, from LRCLIB without requiring an API key.3189 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables searching Genius.com for artists, songs, and albums, retrieving song lyrics, and exploring artist discographies through natural language.3MIT
- AlicenseAqualityDmaintenanceMCP server for Suno music generation API that enables generating lyrics and custom songs with style tags, model selection, and automatic polling for task completion.2MIT
- 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.72 npm3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to understand song lyrics and meaning, find lyrically similar tracks, build mood playlists, and analyze artists and listening data across Spotify, LRCLIB, Last.fm, and ReccoBeats.14MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables LLMs to search, play, and manage music from multiple platforms (NetEase, QQ, Kugou) and local files, with lyrics retrieval and playback control.MIT
TDQS
Scored across 3 tools
search_lyrics and search_songs are the only pair at risk of confusion since lyrics.com conflates title and lyric matching, but the descriptions clearly separate 'fragment of lyrics' from 'named song title' use cases. get_lyrics is unambiguously a fetch-by-id tool.
All three tools follow a consistent snake_case verb_noun pattern (search_lyrics, search_songs, get_lyrics). Search verbs are used uniformly and the fetch verb is distinct.
Three tools is on the lean side, but for the narrow lyrics-lookup domain each has a clear role: find by lyric, find by title, fetch full text. No padding or redundancy.
The core workflow (locate a song by lyric or title, then retrieve its full text with pagination) is fully covered, including edge cases like no_lyrics. Minor gaps exist for artist/album-centric browsing, but agents can work around these via title searches.