sing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUSIC_U | No | Optional. Your NetEase Cloud Music MUSIC_U cookie (from music.163.com in a browser: Developer Tools → Application → Cookies), placed in config.json as {"netease": {"musicU": "..."}}. Needed to download members-only songs; without it only free songs can be downloaded (or you pass an mp3 file directly). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cover_songA | 用你自己的声音翻唱一首歌:照原曲的旋律、断句和伴奏,只把人声换成你的。song 写歌名(可带歌手)或网易云链接(music.163.com、163cn.tv 短链接、App 分享出来的整段文字都行);手里有音频文件就写 file(运行这个服务的电脑上的路径)。一般一两分钟,每首消耗 30 声线积分,一次只唱一首。成品是一个 mp3,连同带时间的歌词一起返回,把链接交给主人就能听。只给主人自己听,不要公开发布。 |
| list_voicesA | 列出声线账号里的音色(克隆的和官方的),★ 是翻唱正在用的。 |
| pointsA | 查声线还剩多少积分(每首翻唱 30)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct action: cover_song creates a cover, list_voices reads the available voices, and points reads the account balance. There is no overlap in purpose and an agent can trivially select the right one.
cover_song and list_voices follow a clear verb_noun pattern, but 'points' is a bare noun with no verb, a minor deviation. Overall still readable and predictable.
Three tools is a lean but coherent surface for a narrow service (check voices, check credits, make a cover). It is on the thin side but each tool earns its place and none are redundant.
The core workflow—inspect voices, verify credits, generate a cover with timed lyrics—is fully covered. Minor gaps exist around voice management (e.g. cloning/deleting voices) and cover job status, but the synchronous cover_song flow mitigates the latter.