mcp-music-forge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| probe_urlA | Detect provider for URL and check whether track is downloadable per provider rules. |
| enqueue_downloadC | Create or dedupe a job and enqueue it for processing. |
| get_job_statusC | Return job status and artifact list. |
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 serves a distinct purpose: probing a URL for downloadability, enqueuing a download job, and checking job status. There is no overlap or ambiguity.
All tools use a consistent verb_noun pattern in snake_case: enqueue_download, get_job_status, probe_url. This follows a predictable and clean naming convention.
With 3 tools covering the core workflow (probe, enqueue, status), the count is well-scoped for a music download service. Not too few or too many.
The toolset covers the primary operations for downloading music from URLs, but lacks advanced features like cancelling jobs or listing all jobs. Minor gap but still functional.