Skip to main content
Glama
fisknils

Spotify API MCP

by fisknils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Spotify API MCP

No user-submitted related servers found.

    Related Servers

    • Spotify MCP

      abenke
      A
      license
      A
      quality
      C
      maintenance
      Enables searching and managing Spotify playlists, tracks, and user information through the Spotify Web API.
      10
      MIT

    • MCP Spotify Server

      superseoworld
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Spotify's music catalog via the Spotify Web API, supporting searches, artist information retrieval, playlist management, and automatic token handling.
      26
      8 npm
      23
      MIT

    • Spotify MCP Server

      EvansLR
      F
      license
      A
      quality
      D
      maintenance
      Enables control of Spotify playback through OAuth authentication, including play/pause, track navigation, volume control, device management, and searching/playing songs by artist or track name.
      11
      1
      -

    • MCP Spotify Server

      fborello
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Spotify through LLMs using OAuth2 authentication. Supports music search, playback control, playlist management, and device management through natural language commands.
      14
      2
      MIT

    • spotify-mcp

      raksix
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Spotify playback via the official Web API, including search/play, pause, skip, volume, queue, and device management.
      60 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: authentication, user profile retrieval, playlist creation, playlist listing, track addition to playlists, and general search. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent 'spotify_verb_noun' pattern with snake_case, such as spotify_authenticate and spotify_add_tracks_to_playlist. This predictability enhances usability and reduces confusion.

    Tool Count5/5

    With 6 tools, the server is well-scoped for basic Spotify API interactions, covering authentication, user data, playlist management, and search. Each tool serves a clear purpose without being excessive or insufficient.

    Completeness4/5

    The toolset covers core Spotify workflows like authentication, user profile access, playlist creation/listing, and search, but lacks update or delete operations for playlists or tracks, which are minor gaps that agents can work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources