mpd-mcp-server

A Go server that bridges Music Player Daemon (MPD) to Model Context Protocol (MCP) by exposing MPD operations (playback controls, search, and playlist management) as MCP tools. Configuration is done via environment variables for the MPD host/port.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Communication mcp mpd music playback playlist go tooling

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

No auth details are provided for the MCP server; if exposed, it may be vulnerable to unauthorized control. TLS/transport security is not described. Configuration uses environment variables for MPD connection parameters, but secret handling is not discussed (likely minimal since only host/port are referenced).

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You have a local or trusted-network MPD instance and want an MCP client/agent to invoke standardized tools for playback and playlist operations.

Avoid When

You need robust auth, encryption guarantees beyond transport, or public exposure to untrusted clients without an external reverse proxy and access control layer.

Use Cases

• Control an MPD music server via an MCP-compatible agent/client
• Search MPD’s music database through MCP tools
• Manage MPD playlists (view, add tracks, clear playlist) from an MCP workflow
• Automate playback actions (play/pause/stop/next/previous) using an agent

Not For

• A general-purpose music streaming API
• Multi-user or internet-facing deployment without additional security controls
• Use cases requiring fine-grained authorization, audit logs, or enterprise compliance out of the box

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

OAuth: No Scopes: No

README does not mention any authentication/authorization mechanism for the MCP server. This suggests either none is built-in or it is not documented.

Pricing

Free tier: No

Requires CC: No

Open-source (MIT) and installed via Go; no pricing information provided.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Side-effecting playback actions: repeated calls may change playback state unexpectedly.
⚠ Playlist-modifying operations (e.g., clear_playlist/add_playlist) may be destructive or non-reversible without prior confirmation.
⚠ Environment variables must be set correctly for MPD_SERVER/MPD_PORT; misconfiguration will prevent tool functionality.

Alternatives

Use MCP tools directly if your MCP client can connect to MPD through its own adapter Build a small custom MCP server around MPD using existing MPD clients Control MPD using MPD’s native protocol (or HTTP bridge) from your application instead of MCP

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mpd-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.