Skip to main content
Glama
Sign In
rachittshah

spotify-llm-mcp

by rachittshah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spotify-llm-mcp

No user-submitted related servers found.

    Related Servers

    • dsh-mcp-expose

      wangpeng123-ux
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a DeepSeek Harness instance — either the whole runtime or one session chosen in the UI — as an MCP Streamable HTTP endpoint on the Harness Web server's origin. Lets other MCP-speaking agents such as Codex or Claude Code delegate tasks, list and read session transcripts, and cancel or inspect running turns using the Harness's own model, tools, workspace and sandbox policy.
      MIT

    • MSIM

      giancbaring
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AnythingLLM to be controlled by any MCP-compatible client via HTTP, SSE, or WebSocket, with automatic workspace selection and background operation.
      MIT

    • WebGPT Codex Bridge

      hsdc1258
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables continuing a local coding task from your own web ChatGPT account by exposing project-scoped read and apply tools over MCP, with no inference API dependency.
      MIT

    • Localbridge-MCP

      danielcanfly
      A
      license
      A
      quality
      A
      maintenance
      LocalBridge MCP is a bridge between an online AI chats and your computer. Most online AI chats can reason, and write code, but they normally cannot touch the local files, terminals, and scripts that make real work happen. This gives a trusted assistant a controlled doorway into a machine you own, so it can inspect files, edit text, search a project, run tests, use Git, and operate a shell.
      17
      3
      Apache 2.0
    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.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have a clear resource+action distinction, but search, play, and resolve_tracks overlap in their underlying lookup/resolution behavior, and the playlist creation/append tools both resolve track picks. Descriptions are usually enough to pick the right one.

    Naming Consistency3/5

    Names are mostly readable but inconsistent: verb_noun forms like play_playlist and list_devices coexist with bare verbs like play and control, plus noun phrases like now_playing and taste_profile. The generic name control is particularly vague.

    Tool Count4/5

    14 tools is a reasonable size for a Spotify assistant covering playback, queue, devices, search, and playlist management. Some search/resolve and playback-control functionality could be consolidated, but the count is not excessive.

    Completeness3/5

    Core workflows are covered: playback control, queue, devices, search, taste profile, and creating/appending playlists. However, there is no way to remove tracks or delete/replace playlists, nor any queue editing or recommendation tool, leaving notable playlist-lifecycle gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources