MCP Claude Spotify

Created By
imprvhuba year ago
An integration that allows Claude Desktop to interact with Spotify using the Model Context Protocol (MCP).
Overview

What is MCP Claude Spotify?

MCP Claude Spotify is an integration that allows Claude Desktop to interact with Spotify using the Model Context Protocol (MCP).

How to use MCP Claude Spotify?

To use MCP Claude Spotify, install it via Smithery or manually, set up your Spotify API credentials, and run the MCP server. Then, use the auth-spotify command in Claude to authenticate your Spotify account.

Key features of MCP Claude Spotify?

  • Spotify authentication
  • Search for tracks, albums, artists, and playlists
  • Playback control (play, pause, next, previous)
  • Create and manage playlists
  • Get personalized recommendations
  • Access user's top played tracks over different time periods

Use cases of MCP Claude Spotify?

  1. Control Spotify playback through Claude Desktop.
  2. Search and manage playlists using voice commands.
  3. Get personalized music recommendations based on listening habits.

FAQ from MCP Claude Spotify?

  • Can I use MCP Claude Spotify without a Spotify account?

No, a Spotify account is required to use this integration.

  • Is there a cost to use MCP Claude Spotify?

No, it is free to use, but a Spotify account is necessary.

  • What are the system requirements?

You need Node.js 16 or higher, a Spotify account, and Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
imprvhub
Star
8
Language
TypeScript
License
MPL-2.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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