Deezer 1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| api_endpointD | 请根据 RapidAPI 页面手动添加端点信息 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'api_endpoint' has a distinct and clear purpose by itself.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'api_endpoint' follows a clear and consistent pattern with no deviations to evaluate.
A single tool is too few for a server named 'Deezer 1 MCP Server', which suggests a music streaming service domain. This minimal set severely limits functionality and likely indicates an incomplete implementation.
The tool set is severely incomplete for a Deezer music API server. With only one generic tool for adding endpoints, there are no specific operations for searching music, managing playlists, or accessing user data, which are core to the domain.