Spotify Playlist Curator MCP Server

Created By
lechiffre1a year ago
MCP server that can analyze your Spotify playlists and use Claude to recommend songs based on the mood, vibe, BPM, and other musical attributes.
Overview

What is Spotify Playlist Curator MCP Server?

Spotify Playlist Curator MCP Server is a tool that analyzes your Spotify playlists and uses Claude AI to recommend songs based on mood, vibe, BPM, and other musical attributes.

How to use Spotify Playlist Curator MCP Server?

To use the server, clone the repository, install dependencies, set up your Spotify Developer credentials, and start the server. Authenticate with your Spotify account to access your playlists and use the available MCP methods.

Key features of Spotify Playlist Curator MCP Server?

  • Connect to your Spotify account and access your playlists
  • Analyze audio features of tracks in your playlists
  • Generate summaries of playlist mood, energy, and tempo
  • Get song recommendations from Claude AI
  • Search for tracks and create new playlists

Use cases of Spotify Playlist Curator MCP Server?

  1. Curating playlists based on specific moods or vibes.
  2. Discovering new music that fits your existing playlists.
  3. Enhancing your listening experience with AI-generated recommendations.

FAQ from Spotify Playlist Curator MCP Server?

  • Can I use this server without a Spotify account?

No, you need a Spotify account to authenticate and access your playlists.

  • Is there a limit to the number of playlists I can analyze?

No, you can analyze as many playlists as you have in your Spotify account.

  • What programming language is this server built with?

The server is built with JavaScript and requires Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lechiffre1
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago