Back to Browse

Musicport MCP Server

Developer ToolsModerate5.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

Spotify search, playback and playlists as MCP tools.

About

Spotify search, playback and playlists as MCP tools.

Security Report

5.6
Moderate5.6Moderate Risk

musicport is a clean, token-env-only Spotify Web API MCP server with no shell execution, no dynamic code evaluation, no hardcoded secrets, and no data exfiltration paths; its network and environment access match its stated purpose. The only notable concern is that the SPOTIFY_API_BASE_URL override would send the Bearer token to whatever host it points to, and the packaged server.json was not provided for review. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

SPOTIFY_ACCESS_TOKENRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-musicport": {
      "env": {
        "SPOTIFY_ACCESS_TOKEN": "your-spotify-access-token-here"
      },
      "args": [
        "-y",
        "@reneturcios/musicport"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

musicport

Spotify search, playback and playlists as MCP tools, talking to the Spotify Web API. musicport is a clean-room rebuild of the core surface of community Spotify MCP servers, under a new name: fresh code, no copied branding.

TOKEN-ENV ONLY. The hosted/community OAuth flow (SPOTIFY_CLIENT_ID / SPOTIFY_CLIENT_SECRET + browser consent + refresh) is NOT reproduced. Tools use SPOTIFY_ACCESS_TOKEN directly as Authorization: Bearer.

Tools (core subset, 12)

search, get_current_user_profile, get_playback_state, play, pause, next_track, previous_track, list_playlists, get_playlist, create_playlist, add_tracks_to_playlist, list_saved_tracks.

Not in this subset: OAuth authorization/refresh flow, track/album/artist detail reads beyond search, audio features/analysis, recommendations, shows/episodes/audiobooks, follow/unfollow artists and users, playlist cover images, playlist item removal/reorder depth, library albums/shows, devices listing and transfer playback, queue management, recently played, top items.

Setup

Obtain a Spotify access token through your own means and set it:

export SPOTIFY_ACCESS_TOKEN=BQ...

Optionally override the API base with SPOTIFY_API_BASE_URL (default https://api.spotify.com/v1). Without the token, every tool call fails with an error naming the missing variable: SPOTIFY_ACCESS_TOKEN environment variable is required.

CLI

npx @reneturcios/musicport search '{"query":"hello"}'
npx @reneturcios/musicport mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "musicport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/musicport", "mcp"],
      "env": { "SPOTIFY_ACCESS_TOKEN": "BQ..." }
    }
  }
}

Docker

docker run -i -e SPOTIFY_ACCESS_TOKEN ghcr.io/cloudcorprecords/musicport

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!