mcp-mpv-player
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| player_playA | Open and play a media file or URL. If mpv is not running, it will be launched automatically. |
| player_pauseA | Toggle pause / resume playback. |
| player_stopA | Stop playback and clear the current file. |
| player_nextB | Skip to the next item in the playlist. |
| player_prevA | Go back to the previous item in the playlist. |
| player_seekC | Seek within the current media. |
| player_set_volumeA | Set playback volume (0–130). 100 is default. |
| player_set_speedA | Set playback speed multiplier. 1.0 = normal speed. |
| player_statusA | Get current playback status: file name, position, duration, volume, speed, pause state. |
| player_shuffleA | Randomly shuffle the current playlist and start playing from the first track. |
| playlist_loadB | Load a saved playlist by name and start playing it. |
| playlist_createB | Create a new playlist with a list of file paths. |
| playlist_addA | Add files to an existing playlist. |
| playlist_removeB | Remove a file from a saved playlist by index (0-based). |
| playlist_listA | List all saved playlists or show contents of a specific playlist. |
| playlist_deleteB | Delete a saved playlist file. |
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 16 tools
Most tools are clearly distinct by action and target resource. The only mild overlap is player_play and playlist_load, since both start playback, but their inputs (file/URL vs saved playlist name) are different enough.
All tools follow the same resource_verb pattern: player_* controls playback and playlist_* manages playlists. The naming is uniform and predictable; player_status is the only noun-style tool but still fits the pattern.
16 tools is a slightly high but justifiable count for a media player server. Each tool maps to a real playback or playlist management operation, though a few could potentially be combined without much loss.
The surface covers core playback transport, volume/speed, status, and full playlist lifecycle (create, add, remove, list, load, delete). Minor gaps exist such as no explicit playlist reordering or mute control, but no critical dead ends for normal usage.