spotify-mcp-server

Created By
NextFirea year ago
Feature-complete Spotify MCP server generated from the OpenAPI specification
Overview

What is Spotify MCP Server?

Spotify MCP Server is a server generated from the OpenAPI specification that allows developers to interact with the Spotify API in a more manageable way.

How to use Spotify MCP Server?

To use the Spotify MCP Server, you need to have the uv tool installed and a Spotify application set up with the appropriate callback URL. Run the provided shell command to generate the client and start the server.

Key features of Spotify MCP Server?

  • Easy integration with the Spotify API.
  • Supports real-time data streaming through server-sent events (SSE).
  • Customizable command configurations for different use cases.

Use cases of Spotify MCP Server?

  1. Building applications that require real-time updates from Spotify.
  2. Creating custom music applications that leverage Spotify's extensive music library.
  3. Developing tools for music analytics and data visualization based on Spotify data.

FAQ from Spotify MCP Server?

  • What are the prerequisites for using Spotify MCP Server?

You need to have the uv tool and a Spotify application with a valid callback URL.

  • Is there a demo available for Spotify MCP Server?

Yes, a demo is provided in the documentation with a screenshot of the interface.

  • What programming language is Spotify MCP Server written in?

The server is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NextFire
Star
0
Language
Python
License
LGPL-3.0 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