A
licenseA
qualityD
maintenanceMCP server for controlling the mpv media player, enabling playback control, music library browsing, YouTube streaming and downloading, and metadata editing from within an MCP client.
17
40 npm
1
MIT
mcp-mpv-player
by guodaxia9527
Related Servers
Alternatives to mcp-mpv-player
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables AI agents to play and control YouTube and TikTok videos through a native mpv player window. It supports browsing subscriptions, searching content, managing playlists, and fetching video metadata using authenticated browser cookies.234 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP control for foobar2000. Control your music player with an AI assistant!6MIT
- AlicenseAqualityCmaintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.1187 npmMIT
- AlicenseNot gradedqualityAmaintenanceVideo player for humans and AI. GUI + CLI + a built-in MCP server (39 tools) to drive playback, clip, transcribe, and search your media library from Claude, Cursor, or any MCP client. Local Whisper subtitles. MIT, local-first.MIT
- AlicenseAqualityDmaintenanceMCP server that enables natural language control of internet radio from Claude Code, with access to 30,000+ global stations, auto-playback via mpv, and a real-time status line with audio spectrum visualization.7MIT
TDQS
A3.6/5.0
Scored across 16 tools
Disambiguation4/5
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.
Naming Consistency5/5
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.
Tool Count4/5
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.
Completeness4/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues