Mpv MCP Server

MCP server for controlling mpv media player — playback, playlists, YouTube streaming and downloading

Local serverstdioGo

What is the Mpv MCP server?

MCP server for controlling mpv media player — playback, playlists, YouTube streaming and downloading. The mpv mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 4 defined tools rather than through you.

What it actually does

MCP server for controlling mpv media player. Browse your music library, control playback, stream from YouTube, and download tracks — all from inside an MCP client like Claude Code.

Adding it to your client

The server ships on npm as mpv-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • Playback — The Playback tool exposed by this server
  • Library — The Library tool exposed by this server
  • YouTube — The YouTube tool exposed by this server
  • Metadata — Both tools infer artist/title from the "Artist - Title" filename pattern. Requires ffmpeg (includes ffprobe)

Configuration

You will need 4 environment variables: MPV_PATH, MPV_MEDIA_DIRS, MPV_DOWNLOAD_DIR, MPV_IPC_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • mpv — media player (must be on your PATH, or set MPV_PATH) - Node.js 22+ - yt-dlp (optional) — required for YouTube streaming and downloading - ffmpeg (optional) — required for audio extraction, metadata reading (ffprobe), and tagging

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mpv mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mpv's toolset — Playback, Library, YouTube and 1 more — is a fair guide to whether it matches your workflow. It is maintained by arijit-gogoi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mpv's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
PlaybackThe Playback tool exposed by this server.
LibraryThe Library tool exposed by this server.
YouTubeThe YouTube tool exposed by this server.
MetadataBoth tools infer artist/title from the "Artist - Title" filename pattern. Requires [ffmpeg](https://ffmpeg.org/) (includes ffprobe).

How to install the Mpv MCP server

{
  "mcpServers": {
    "mpv": {
      "command": "npx",
      "args": ["-y", "mpv-mcp-server"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • mpv — media player (must be on your PATH, or set MPV_PATH) - Node.js 22+ - yt-dlp (optional) — required for YouTube streaming and downloading - ffmpeg (optional) — required for audio extraction, metadata reading (ffprobe), and tagging
VariableDescriptionRequired
MPV_PATHFilesystem location the server is allowed to use.Optional
MPV_MEDIA_DIRSFilesystem location the server is allowed to use.Optional
MPV_DOWNLOAD_DIRFilesystem location the server is allowed to use.Optional
MPV_IPC_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Mpv to Playback.
  • Use Mpv to Library.
  • Use Mpv to YouTube.

Frequently asked questions

It connects Mpv to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (Playback, Library, YouTube, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mpv directly.