A
licenseA
qualityB
maintenanceMCP server for lyrics.com that enables searching songs by lyrics or title and retrieving full lyrics, with no API key required.
3
99
MIT
mcp-lrclib
by smeet666
Related Servers
Alternatives to mcp-lrclib
Related Servers
- FlicenseBqualityBmaintenanceA local music retrieval MCP server that lets users search, download, and organize songs via natural language, with lyrics matching from NetEase Cloud Music and LRCLIB, plus local library indexing through SQLite.5-
- AlicenseNot gradedqualityCmaintenanceAn 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.1163Apache 2.0
- 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
- AlicenseNot gradedqualityBmaintenanceBridges multiple lyrics providers (LRCLIB, Genius, Musixmatch, Melon) into a single toolchain accessible via MCP, HTTP, or CLI.741MIT
- AlicenseNot gradedqualityAmaintenanceMCP 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
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.MIT
TDQS
A4.7/5.0
Scored across 3 tools
Disambiguation4/5
The tools are mostly distinct: search_tracks finds tracks by query while get_track fetches a specific track by ID, and get_lyrics retrieves lyric content. There is minor overlap in that both search_tracks and get_track return metadata, but their purposes are clearly separated by search vs. direct lookup.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: search_tracks, get_lyrics, and get_track. The naming is predictable and makes the action and resource type immediately clear.
Tool Count5/5
Three tools is an appropriate scope for an LRCLIB lyrics server. Each tool covers a distinct part of the workflow: searching, fetching lyrics, and fetching track metadata, with no unnecessary duplication.
Completeness5/5
The tool surface covers the full read-only workflow for this domain: discover tracks, inspect metadata, and fetch either plain or synced lyrics. Descriptions also handle edge cases like truncation, instrumental tracks, and timing checks, so there are no obvious dead ends.
Maintenance
ActivityActive
ResponsivenessUnresponsive