Provides play and pause controls for Home Assistant media players (TV, projector, speaker, etc.), enabling automated playback control through Home Assistant's media player API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Media Player pause the living room TV"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Dopamine-driven development, minus the binge-watching.
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
Related MCP server: MCP Home Assistant
Node.js 18 or higher (for native fetch and ES modules)
A running Home Assistant instance
A valid Home Assistant long-lived access token
Clone the repository
Install dependencies
npm installConfigure MCP integration
Copy mcp.json.example to your MCP config location (e.g., ~/.cursor/mcp.json) and fill in your real values:
{
"mcpServers": {
"MediaPlayer": {
"command": "node",
"args": [
"/absolute/path/to/your/media-player-mcp.js"
],
"env": {
"HA_URL": "http://your-ha-url:8123",
"HA_TOKEN": "your_home_assistant_long_lived_token",
"ENTITY_ID": "media_player.your_media_player_entity"
}
}
}
}Add Cursor rules for automation
To automate the play/pause while the agent is working, copy the rules in cursor-rules.example into your Cursor rules configuration. This configures a system prompt rule that ensures the play/pause tools are called at the appropriate times.
Start the MCP server
npm startOr, let your MCP client launch it automatically.
MIT
Pause the media player via Home Assistant.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavior disclosure. It only states the action without revealing any side effects, prerequisites, or state changes, which is insufficient for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no unnecessary words, making it highly concise and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (no parameters, no output schema, no annotations), the description is largely sufficient. However, it could improve by mentioning whether a specific media player entity is required or if it affects all players.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema is empty with 0 parameters, and the description adds no parameter information. Per calibration, 0 parameters receive a baseline score of 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (pause) and the resource (media player). It effectively distinguishes from the sibling tool play_media_player by specifying the opposite action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when wanting to pause a media player, and the sibling tool name clarifies the alternative. However, it does not explicitly state when not to use it or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Play/resume the media player via Home Assistant.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It explains the action (play/resume) sufficiently, though it could mention if it restarts or resumes from pause. It is adequate for a simple tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that is front-loaded with the essential information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description fully covers the tool's purpose and behavior. It is complete for a simple action like playing a media player.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the description need not add parameter information. It effectively conveys that no inputs are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (play/resume) and the resource (media player via Home Assistant). It implicitly distinguishes from the sibling tool `pause_media_player` since play is the opposite of pause.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the action is straightforward, the description does not explicitly state when to use this tool versus the sibling `pause_media_player`. The guidance is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The two tools have completely distinct purposes: one pauses, one plays. There is no overlap or confusion.
Both tool names follow a consistent 'verb_noun' pattern (pause_media_player, play_media_player).
With only 2 tools, the set feels thin for a media player. While it's not extreme, it falls into the borderline range where more tools would be expected.
The tool surface is severely incomplete. A media player typically requires stop, skip, volume control, etc., which are all missing.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Build and supervise fleets of agents from Claude Code, Codex or Cursor. Connects over OAuth.
Let ChatGPT, Claude & Cursor use your Mac: email, calendar, iMessage, Teams, files. Local, free.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
The media memory layer for AI agents and their humans. Your AI client gets 29 tools to search your collection, add items, update ratings, preview music, and find patterns across everything you've read, watched, and listened to.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielsims/mcp-media-player'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
