spotify_mcp

Created By
jmoro0408a year ago
MCP Server to control Spotify
Overview

What is spotify_mcp?

spotify_mcp is a project that integrates with Spotify using the Model Context Protocol (MCP), allowing users to control playback, access user data, and interact with the Spotify API seamlessly.

How to use spotify_mcp?

To use spotify_mcp, clone the repository, set up a virtual environment, install dependencies, configure your Spotify API credentials, and run the server to start interacting with the Spotify API through MCP tools.

Key features of spotify_mcp?

  • Control Spotify playback (play, pause, skip, shuffle)
  • Access user playlists and recently played songs
  • Generate playlists based on user preferences
  • Integration with MCP for enhanced functionality

Use cases of spotify_mcp?

  1. Automating music playback based on user preferences.
  2. Creating personalized playlists using LLM capabilities.
  3. Accessing and managing Spotify playlists programmatically.

FAQ from spotify_mcp?

  • Can I control Spotify playback with this project?

Yes! You can play, pause, skip songs, and more.

  • Do I need to set up Spotify API credentials?

Yes, you need to create an application on the Spotify Developer Dashboard and set up your credentials.

  • Is this project open-source?

Yes! The project is available on GitHub under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jmoro0408
Star
0
Language
Python
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)

a day ago