lastfm-mcp
Related Servers
Alternatives to lastfm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA 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.24MIT
- AlicenseNot gradedqualityBmaintenanceUnofficial, 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.53MIT
- AlicenseAqualityCmaintenanceMCP 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.2046 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceAn 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
- AlicenseNot gradedqualityCmaintenanceEnables 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 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents the ability to listen to and understand music/audio files, enabling semantic analysis, stem separation, lyrics transcription, and signal processing via tool calls.1MIT
TDQS
Scored across 16 tools
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.
All tools follow a consistent 'lastfm_<verb>_<resource>' pattern in snake_case, making it predictable and easy to navigate.
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.
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.