mpd

mpd-mcp-server exposes common MPD operations as MCP tools. After starting the server, clients can call tools such as search, play, pause, stop, resume, next, previous, get_status, get_current_song, get_playlist, clear_playlist, and add_playlist to control an MPD instance. The server connects to an MPD daemon using the configured MPD_SERVER and MPD_PORT, and translates MCP tool invocations into MPD protocol commands, returning results in MCP-compatible responses. This enables integrated automation and scripting workflows that manage playback, playlists, and song queries against MPD without needing direct MPD protocol handling in each client.

To use, ensure MPD is reachable from the host running mpd-mcp-server and that the required environment variables (MPD_SERVER and MPD_PORT) are set if you are not using defaults. Tools can be invoked by name (e.g., mpd search, mpd play, mpd get_status) depending on your MCP client integration. The server provides a straightforward mapping between MCP tool names and MPD functionality, allowing you to perform typical DJ-like operations programmatically.

Prerequisites:

• Go 1.24.1 or later
• MPD server running and accessible
• MCP protocol-compatible client

Installation steps:

1. Install the server binary:

go install github.com/gamoutatsumi/mpd-mcp-server@latest

2. (Optional) Verify the binary is in your PATH:

which mpd-mcp-server
# or on Windows: where mpd-mcp-server

3. Configure environment variables for MPD connection (if needed):

export MPD_SERVER=localhost
export MPD_PORT=6600

4. Run the server:

mpd-mcp-server

5. If you need to run in the background or as a service, create a systemd unit or equivalent, ensuring the MPD_SERVER and MPD_PORT environment variables are set for the service.

Notes:

• The MPD connection is configured via environment variables MPD_SERVER and MPD_PORT. If your MPD uses a different host/port, adjust accordingly.
• Ensure network access between the mpd-mcp-server host and the MPD server (e.g., not blocked by firewalls).
• If MPD requires authentication, you may need to configure the MPD client credentials in the environment or through MPD's internal configuration, depending on the server implementation.
• The available tools correspond to typical MPD operations: search, play, pause, stop, resume, next, previous, get_status, get_current_song, get_playlist, clear_playlist, add_playlist.
• Check logs if a tool call fails to diagnose whether the issue is MPD connectivity, permissions, or MCP client usage.