Mpv Mcp Server
Let your coding agent drive mpv for local playback, playlists, library scan paths, YouTube stream, and downloads via MCP.
Overview
io.github.arijit-gogoi/mpv-mcp-server is a MCP server for the Build phase that controls mpv playback, playlists, YouTube streaming, and downloads for agent-driven media workflows.
What is this MCP server?
- Playback and playlist control for mpv through MCP tool calls
- YouTube streaming and download support with MPV_DOWNLOAD_DIR configuration
- Env knobs: MPV_PATH, MPV_IPC_PATH, MPV_MEDIA_DIRS (defaults ~/Music, ~/Videos)
- npm package mpv-mcp-server v1.2.0 with stdio transport
- Cross-platform IPC: named pipe on Windows, Unix socket on macOS and Linux
- npm package mpv-mcp-server version 1.2.0
- Four documented environment variables (MPV_PATH, MPV_IPC_PATH, MPV_MEDIA_DIRS, MPV_DOWNLOAD_DIR)
- Default media directories ~/Music and ~/Videos per registry manifest
What problem does it solve?
Builders want agents to start, queue, and fetch media locally without writing custom mpv IPC scripts for every task.
Who is it for?
Solo developers who already use mpv and want quick agent-driven playback and playlist automation on their machine.
Skip if: Teams needing cloud CDN streaming, team-wide rights-managed media libraries, or headless CI with no desktop mpv install.
What do I get? / Deliverables
Once registered, your agent can invoke MCP tools to control mpv, scan default or custom media dirs, and download YouTube content to a chosen folder.
- Working stdio MCP connection to mpv control tools
- Configured media scan paths and download directory for agent use
- Agent-callable playback, playlist, and YouTube stream/download actions
Recommended MCP Servers
Journey fit
Canonical Build shelf because the server extends your agent toolchain by integrating a local media player—not a launch, grow, or production monitoring concern. Integrations fits IPC-linked mpv control, configurable media directories, and YouTube download hooks exposed as MCP tools to the host agent.
How it compares
Local mpv IPC MCP integration, not a browser automation or music SaaS API connector.
Common Questions / FAQ
Who is io.github.arijit-gogoi/mpv-mcp-server for?
It is for developers who run mpv locally and want MCP-capable agents to handle playback, playlists, and YouTube actions.
When should I use io.github.arijit-gogoi/mpv-mcp-server?
Use it during Build when you integrate desktop media into agent workflows—demos, content prep, or hands-free playlist control while coding.
How do I add io.github.arijit-gogoi/mpv-mcp-server to my agent?
Install npm package mpv-mcp-server 1.2.0, ensure mpv is on PATH or set MPV_PATH, configure optional IPC and media env vars, and add stdio MCP server entry in your client.