MCP server for the 残像API 网抑云音乐 (NetEase Cloud Music) search & playback API.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-server-cxzja-music","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-server-cxzja-music MCP (Model Context Protocol) server exposing the **残像API 网抑云音乐** (NetEase Cloud Music) search & playback API. Lets AI clients search songs by keyword and resolve them into direct audio URLs, covers and lyrics. API docs: <https://api.cxzja.cn/docx-wyymusic.html> ## Features - `search_music(keyword, n, br)` — search and return song details at index `n` - `resolve_music(song_id, br)` — resolve a song id into a direct audio URL - `fetch_lyrics(keyword, n)` — return LRC lyrics for a search result Supports multiple audio qualities: `jymaster`, `dolby`, `sky`, `hires`, `lossless`, `exhigh`, `standard`. ## Quick start ```bash pip install mcp-server-cxzja-music mcp-server-cxzja-music # stdio (default) mcp-server-cxzja-music --transport streamable-http --port 8000 ``` Or run directly without installing: ```bash uvx mcp-server-cxzja-music ``` ## Token The API needs your personal 残像API token. No token is baked into the package. It is resolved in this order: 1. per-call `token` tool parameter 2. `--token` CLI argument 3. `CXZJA_TOKEN` environment variable If none is set, the tools return a clear error. Recommended for imcp.pro: set `CXZJA_TOKEN` in the MCP service's environment (or pass `--token=<YOUR_TOKEN>` as a CLI argument if the platform supports it). For a shared/public deployment, prefer setting `CXZJA_TOKEN` (or a per-call token) over relying on the baked default. ## imcp.pro configuration Create an MCP service with: - Transport: **stdio** - Command: `uvx` - Args: `mcp-server-cxzja-music` - Environment: add `CXZJA_TOKEN=<your token>` (if the platform exposes an environment-variables field), otherwise append ` --token=<your token>` to the Args field. Then bind it to an Agent and export the gateway WebSocket into Xiaozhi.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.