Skip to main content
Glama
lastfm-mcp

lastfm-mcp

by dkfancska

Related Servers

Alternatives to lastfm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that gives AI agents access to a user's Last.fm listening history, including recent plays, top tracks, artists and albums, loved tracks, tags, and similar-track/artist data. This lets the agent inspect someone's taste and discover music they haven't heard before, which it can then play through its own music tool.
      24
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Unofficial, read-only access to your Last.fm listening history, charts, loved tracks, and artist, album and track lookups. Connect to https://lastfm-mcp.com/mcp and sign in with Last.fm. Not affiliated with Last.fm.
      53
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for Spotify that enables playlist building and music discovery through 19 tools, allowing LLM agents to search tracks/artists/albums, manage playlists, control playback, and access personal listening data.
      20
      46 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      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
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fetch music artist, album, and track metadata, search tracks, discover similar artists, and list top tracks, tags, charts, and user listening stats through MCP tools.
      74 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource (album, artist, track, user) and action (get info, get top, search, similar), with no overlap in purpose. An agent can clearly distinguish between them.

    Naming Consistency5/5

    All tools follow a consistent 'lastfm_<verb>_<resource>' pattern in snake_case, making it predictable and easy to navigate.

    Tool Count4/5

    16 tools is appropriate for a music discovery service covering albums, artists, tracks, and users, though slightly more than the typical 3-15 range. Still well-scoped.

    Completeness4/5

    Covers core read operations for artists, albums, tracks, and users including search and top lists. Lacks write operations (like love/unlove tracks) and some niche endpoints (e.g., tags, events), but the read surface is solid.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues