MCP Media Player MCP Server

MCP server for controlling a media player via Home Assistant.

Local serverstdio

What is the MCP Media Player MCP server?

If you already use MCP Media Player, the mcp media player mcp server is the piece that lets your assistant work with it directly. MCP server for controlling a media player via Home Assistant.

What the server does

You could just watch one episode. Or you could automate the pause button and pretend you have self-control. MCP Media Player connects any Home Assistant media player (TV, projector, speaker, etc.) to the Cursor coding environment. Play media while your agent works; when it's done, so is your break.

  • Exposes play and pause controls for a media player as MCP tools
  • Integrates with Home Assistant's media player API
  • Provides Cursor rules for automating playback while the agent is working

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: HA_URL, HA_TOKEN, ENTITY_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 18 or higher (for native fetch and ES modules) - A running Home Assistant instance - A valid Home Assistant long-lived access token

Worth knowing first

  • 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.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by danielsims; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Configuration

  • Node.js 18 or higher (for native fetch and ES modules) - A running Home Assistant instance - A valid Home Assistant long-lived access token
VariableDescriptionRequired
HA_URLEndpoint or connection string the server talks to.Yes
HA_TOKENCredential the server authenticates with.Yes
ENTITY_IDConfiguration value read at startup.Optional

Frequently asked questions

It connects MCP Media Player to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with MCP Media Player directly.