🎧 MCP Playlist Generator
@m4dd0c
About 🎧 MCP Playlist Generator
A Model Context Protocol (MCP) server that enables AI agents to create and manage music playlists through context-aware API endpoints.
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is 🎧 MCP Playlist Generator?
🎧 MCP Playlist Generator is a Model Context Protocol server that works with Claude or any AI assistant supporting tool usage. It scans local music files, reads metadata with mutagen, and creates .m3u playlists on the user’s PC based on a requested mood or theme. The playlist is saved to a directory the user specifies.
How to use 🎧 MCP Playlist Generator?
Install Python dependencies with pip install uv mutagen, then clone the repo and run uvicorn mcp_server:app --reload. The server listens for requests; users ask their AI assistant (e.g., “make a happy vibe playlist”) and the assistant invokes the server tool. After creation, users should re-index their music app.
Key features of 🎧 MCP Playlist Generator
- Generates
.m3uplaylists from local music files. - Filters songs by mood or theme using metadata.
- Leverages
mutagenfor metadata extraction (genre, title, artist). - Saves playlist to a user‑specified directory.
- Works with any LLM agent supporting tool calls.
- Built with Python and the
uvasync web server.
Use cases of 🎧 MCP Playlist Generator
- Create a “chill evening playlist” from your personal library.
- Generate a “happy vibe” playlist on demand via a Claude prompt.
- Automate mood‑based playlist creation without manual sorting.
- Integrate with any AI assistant that can invoke MCP tools.
FAQ from 🎧 MCP Playlist Generator
How is this different from a regular playlist generator?
It runs locally on your machine, scanning your own music files, and is triggered by an AI assistant via the MCP protocol rather than using a web service or manual curation.
What runtime or dependencies are required?
Python with the uv and mutagen packages installed. The server runs as a Uvicorn ASGI application.
Where are playlists saved?
The user specifies the save directory in their request. No default fallback is documented.
Which audio formats are supported?
The README only mentions reading metadata with mutagen and creating .m3u playlists. It does not list specific audio file formats.
What transport or authentication does the server use?
The server uses HTTP (Uvicorn). No authentication mechanism is described.
Frequently asked questions
How is this different from a regular playlist generator?
It runs locally on your machine, scanning your own music files, and is triggered by an AI assistant via the MCP protocol rather than using a web service or manual curation.
What runtime or dependencies are required?
Python with the `uv` and `mutagen` packages installed. The server runs as a Uvicorn ASGI application.
Where are playlists saved?
The user specifies the save directory in their request. No default fallback is documented.
Which audio formats are supported?
The README only mentions reading metadata with `mutagen` and creating `.m3u` playlists. It does not list specific audio file formats.
What transport or authentication does the server use?
The server uses HTTP (Uvicorn). No authentication mechanism is described.
Basic information
More Developer Tools MCP servers

Termany
thinkany-aiAgent-Native Terminal

SSH MCP Server
hypnosisSSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.
LocalCan
LocalCanGives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
OrangePro
Aamir SiddiquiOrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
Comments