Skip to main content
Glama
rollecode

lastfm-mcp

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to lastfm-mcp

No user-submitted related servers found.

    Related Servers

    • Last.fm MCP Server

      elcachorrohumano
      F
      license
      B
      quality
      D
      maintenance
      Enables interaction with Last.fm music data including searching for artists, albums, and tracks, accessing user listening history, and managing music preferences. Supports both read-only operations and authenticated write operations like scrobbling and loving tracks.
      34
      5
      -

    • mcp-lastfm

      kud
      A
      license
      B
      quality
      B
      maintenance
      Provides 41 read-only tools to search and browse Last.fm data, including artists, albums, tracks, user scrobble history, and charts.
      41
      6 npm
      MIT

    • spotify-mcp

      Stipe15
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude to manage Spotify playlists and analyze personal listening history, including account reads, playlist writes, local analytics from data exports, and building playlists from track lists.
      35
      MIT

    • lastfm-mcp

      rianvdm
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for Last.fm. Gives AI assistants access to your listening history, music discovery, and detailed track/artist/album information.
      47
      MIT

    • spotify-library-mcp

      oliver-virt
      A
      license
      B
      quality
      B
      maintenance
      Enables you to manage your personal Spotify library from Claude or a CLI, including organizing playlists, merging and deleting playlists, saving tracks, searching with artist verification, and querying top tracks, artists, and recently played items.
      27
      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.6/5.0

    Scored across 58 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action (artist vs album vs track, user-specific vs global charts), and descriptions clarify the few near-pairs like get_album_tags vs get_album_top_tags. However, get_top_tags and get_chart_top_tags appear to describe essentially the same global tag ranking, which could cause an agent to misselect.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern: get_*, search_*, add_*, remove_*, love/unlove, scrobble_tracks, update_now_playing. Auth tools also align with start/finish/get/clear, so a predictable rhythm is maintained throughout.

    Tool Count1/5

    At 58 tools, the server is far beyond the recommended scope and is an extreme count for an MCP agent to reason over. The combinatorial explosion of similar endpoints (weekly charts, top tags, per-entity tags) makes navigation burdensome, even if each endpoint maps to a real Last.fm API method.

    Completeness4/5

    The surface covers the core Last.fm domain well: user history and charts, global/geo/tag charts, album/artist/track metadata and search, tagging, love/unlove, scrobbling, now playing, and authentication. Minor gaps exist around events and some less common API endpoints, but these are workable omissions rather than dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources