Skip to main content
Glama
latiftplgu

Spotify MCP Server

by latiftplgu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Spotify MCP Server

No user-submitted related servers found.

    Related Servers

    • Spotify MCP Server

      llyfn
      A
      license
      B
      quality
      C
      maintenance
      MCP server for the Spotify Web API — gives Claude and other AI assistants tools to search music, control playback, manage playlists, library, and podcasts.
      59
      MIT

    • Spotify MCP Server

      nlevy
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides Spotify integration, allowing AI assistants and applications to interact with Spotify's music streaming service.
      12
      1
      MIT

    • spotify-mcp-server

      qchuchu
      A
      license
      Not graded
      quality
      D
      maintenance
      An unofficial MCP server that provides access to Spotify's Web API through the Model Context Protocol, enabling AI assistants to search music, manage playlists, and control playback.
      6
      9
      ISC
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear boundaries, such as get_album vs get_album_tracks or add_to_playlist vs add_to_queue. However, some overlap exists, like remove_from_playlist and remove_tracks, which could cause confusion about whether they affect playlists or the user's library. The descriptions help clarify, but the similar naming and overlapping concepts present minor ambiguity.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern throughout, such as get_album, create_playlist, and search_tracks. The naming is highly predictable and readable, with no mixing of conventions or inconsistent verb styles. This uniformity makes it easy for agents to understand and predict tool functions.

    Tool Count2/5

    With 41 tools, the count is excessive for a single server, making it feel heavy and potentially overwhelming for agents. While Spotify's API is extensive, many tools could be consolidated (e.g., multiple search tools or overlapping get functions). A more focused set of 15-25 tools would be better scoped for coherence and usability.

    Completeness5/5

    The tool surface provides comprehensive coverage of Spotify's core functionalities, including CRUD operations for playlists and tracks, playback control, user profile management, and extensive search capabilities. There are no obvious gaps; agents can perform full lifecycle actions like creating, modifying, and deleting content, along with discovery and analytics, ensuring no dead ends in typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources