Skip to main content
Glama
kud

mcp-lastfm

by kud

Related Servers

Alternatives to mcp-lastfm

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables music discovery and recommendations through the free Last.fm API by exposing tools for artist and track search, similarity-based suggestions, genre or mood-based discovery, and personalized recommendations built from a Last.fm user's listening history.
      -
    • 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
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables reading and writing Last.fm data from Claude, with all 44 read methods and 10 write methods exposed as tools, including scrobbling, loving tracks, and tagging.
      59
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for the Last.fm API, exposing artist, album, track, chart, and user data as read-only tools. Supports optional writes, auth, and experimental methods over stdio or HTTP.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to Last.fm listening history, enabling music discovery and rediscovery through recent scrobbles, top items, artist history checks, and rediscovery candidates for public profiles.
      4
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a self-hosted SQLite master of a user's complete Last.fm listening history over Streamable HTTP with OAuth 2.1, so ChatGPT or Claude can answer questions about any date range without hitting the Last.fm API. Provides 32 tools covering recent plays, period rankings, range comparisons, artist listening intensity, session segmentation, and shifts in taste over time.
      14 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 41 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., get_artist vs get_artist_top_albums). Even tools that seem similar like get_tag_top_albums and get_album_top_tags are clearly inverses with different inputs and outputs, leaving no ambiguity.

    Naming Consistency5/5

    All tool names follow a verb_noun pattern using snake_case (correct_, get_, search_). The naming is predictable, making it easy for an agent to infer functionality from the name.

    Tool Count4/5

    41 tools is high but justified by the broad Last.fm API domain (artists, albums, tracks, tags, users, charts, geo). The count is within the upper bound of a well-scoped set; it covers essential endpoints without being excessive.

    Completeness4/5

    The tool set provides thorough read coverage of Last.fm data: artists, albums, tracks, tags, users, charts, and search. Minor gaps like missing artist events or user library management are acceptable for a read-only server, and core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues