MCP QQ Music Test Server
Related Servers
Alternatives to MCP QQ Music Test Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceMulti-source music search and playback MCP server supporting QQ Music, NetEase Cloud, and local files with playlist management.32MIT
- AlicenseAqualityDmaintenanceMCP server for controlling local music playback via NetEase Cloud Music, enabling search, play, pause, skip, and lyrics display through a local web player.1377MIT
- 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
- AlicenseAqualityDmaintenanceIntegrates QQ Music API with MCP, enabling LLMs to search music, retrieve song details, lyrics, and playback URLs.104MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.MIT
- AlicenseAqualityBmaintenanceA read-only MCP server for NetEase Cloud Music data, enabling querying of songs, artists, albums, playlists, lyrics, and user library through tools like search and get details.153MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_music' has a clear, distinct purpose that cannot be confused with any other tool in this server.
The naming pattern cannot be evaluated for consistency across multiple tools, but the single tool name 'search_music' follows a clear verb_noun convention that is appropriate and readable. There are no inconsistencies to assess.
A single tool is too few for a music server's apparent scope, which typically involves operations like playing, pausing, getting recommendations, managing playlists, or accessing user libraries. This minimal set severely limits functionality and suggests an incomplete implementation.
The server is severely incomplete for a music domain, offering only search functionality without any way to play, queue, control playback, access user data, or manage music collections. This creates significant gaps that will cause agent failures in typical music-related workflows.