mcpField
S
SpotifyMcpServer

SpotifyMcpServer

Local
github.com/devoctomyGames & Entertainment0Updated 78w ago

About SpotifyMcpServer

SpotifyMcpServer is a .NET 8 STDIO MCP server that provides access to Spotify user playlists. It is configured with Spotify API credentials and includes a tool to retrieve playlists by user ID.

Key features

  1. 01STDIO MCP server for Spotify
  2. 02Retrieve playlists by user ID
  3. 03Uses Spotify API credentials

Use cases

  1. 01Retrieve a Spotify user's playlists
  2. 02Provide playlist lookup to an MCP client

MCP support

Exposes a GetUserPlaylists tool over STDIO for MCP clients, retrieving playlists for a specified Spotify user ID.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Spotify MCP Server

A simple STDIO MCP server for Spotify.

After not having any luck with existing tools that required a return url, I decided to write one myself.

Requirements
  • .NET 8.0 SDK

Following environment variables

SPOTIFY_API_CLIENTID
SPOTIFY_API_SECRET

You can get these by creating an application in Spotify developer portal. You can enter anything for the return url as it will not be used, as long as it accepts what you enter.

Configure in Cursor
{
  "mcpServers": {
    "spotify": {
      "command": "<full path>\\SpotifyMcpServer.exe",
      "args": []
    }
  }
}
Current Tools
  1. GetUserPlaylists - Gets playlists for a specific user by user id.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.