MyMusik MCP
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.
Pair with the running MyMusik app using mymusik-mcp pair, then restart the connector.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mymusik_playbackA | Control the current MyMusik queue. Resume or pause playback, skip to the next track, or go back one track. Requires playback access. To play a particular song, album or playlist by name, use the app's search and API tools. |
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
There is only one tool in the set, so there is no ambiguity about which tool to select. Its purpose—controlling the current playback queue—is clearly stated and distinct from search/API tools mentioned elsewhere.
The single tool uses a clear snake_case server-prefixed pattern, mymusik_playback. With only one tool, there is no inconsistency in convention.
A single tool is too thin for a server named MyMusik MCP, which implies broader music control. The one tool bundles several playback actions but leaves the overall server surface underspecified.
The tool covers resume, pause, next, and previous, but lacks play-by-name, queue inspection, volume, seek, shuffle, and other common playback operations. The description explicitly points users to other tools for playing a particular song, album, or playlist, which is a notable gap.