Spotify MCP Server

Created By
Jopgooda year ago
A Media Control Protocol server for controlling Spotify playback
Overview

what is Spotify MCP Server?

Spotify MCP Server is a Media Control Protocol server that provides a unified interface for controlling Spotify playback across different devices and applications.

how to use Spotify MCP Server?

To use the Spotify MCP Server, clone the repository, install the dependencies, set up your environment variables, and start the server. You can then authenticate with Spotify and use the API endpoints to control playback.

key features of Spotify MCP Server?

  • Control Spotify playback (play, pause, skip, previous)
  • Adjust volume
  • Search for and play specific tracks, albums, or playlists
  • Get current playback information
  • RESTful API for easy integration with other applications
  • AI Assistant integration for controlling Spotify with natural language
  • Voice control interface for speaking commands to Spotify

use cases of Spotify MCP Server?

  1. Controlling Spotify playback from a web application.
  2. Integrating Spotify control into AI assistants.
  3. Using voice commands to manage music playback hands-free.

FAQ from Spotify MCP Server?

  • Do I need a Spotify Premium account to use this?

Yes, a Spotify Premium account is required to control playback.

  • Can I use this server with any device?

Yes, as long as the device can connect to the server and has Spotify installed.

  • Is there a command line interface available?

Yes, a command line interface is included for controlling Spotify from the terminal.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Jopgood
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Voyei

2 hours ago
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