MCP server for Music Assistant – control playback, browse libraries, and manage queues via AI assistants
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"music-assistant-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# music-assistant-mcp An [MCP](https://modelcontextprotocol.io/) server that wraps the [Music Assistant](https://music-assistant.io/) client library, exposing music search, library browsing, playback control, queue management, and playlist curation to AI assistants. ## Configuring and Installing ### Generate a Long-Lived Access Token First 1. Navigate to your Music Assistant instance at `http://<your-ma-host>:8095/#/settings/profile`. 2. Scroll down to the **Long-lived access token** section and click **+ Create new token**. 3. Assign a name and submit. 4. Copy the generated token value to a safe place — you will need it in the setup steps below. ### Get Environment Variables Ready To reach a Music Assistant instance, you'll need to set some environment variables: | Variable | Required | Description | |----------|----------|-------------| | `MA_SERVER_URL` | Yes (or `MA_HOST`) | Full URL like `http://10.10.10.10:8095` | | `MA_HOST` | No | Hostname, combined with `MA_PORT` | | `MA_PORT` | No | Defaults to `8095` | | `MA_TOKEN` | Yes | Bearer token generated by Music Assistant | You don't necessarily have to set these in your shell in a persistent way. These variables can typically be injected into the MCP server's execution context as necessary as shown in the examples below. ### Claude Integration Many will want to use this MCP server from Claude Desktop, Claude Code, or another MCP host. You can add the MCP server to Claude Code with the CLI like this: ```bash claude mcp add --transport stdio music-assistant \ --env MA_SERVER_URL=http://your-ma-host:8095 \ --env MA_TOKEN=your-token \ -- uvx music-assistant-mcp ``` Or add it to your Claude Code or Claude Desktop MCP configuration files as follows: ```json { "mcpServers": { "music-assistant": { "command": "uvx", "args": ["music-assistant-mcp@latest"], "env": { "MA_SERVER_URL": "http://your-ma-host:8095", "MA_TOKEN": "your-token" } } } } ``` ## …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.