Skip to main content
Glama
dkfancska

lastfm-mcp

by dkfancska
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to lastfm-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      207 npm
      49
      MIT

    • mcp-spotify

      obrien-matthew
      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
      28 PyPI
      MIT

    • lastfm-mcp

      ndyakov
      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

    • last-fm

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      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.
      391 npm
      1
      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.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 issues

    Resources