Skip to main content
Glama
Dthen

listenbrainz-mcp

by Dthen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to listenbrainz-mcp

No user-submitted related servers found.

    Related Servers

    • lastfm-mcp

      ndyakov
      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

    • lastfm-mcp

      rollecode
      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.
      58
      MIT

    • musicbrainz-mcp-server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      Search artists, releases, recordings, works, and labels; traverse relationships; resolve ISRC/ISWC/barcode; fetch cover art via MCP. STDIO or Streamable HTTP.
      55 npm
      1
      Apache 2.0

    • youtube-music-mcp

      ElisonSz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching YouTube Music and managing playlists through read and confirmation-gated write tools over STDIO. Supports identity checks, song search, playlist listing/retrieval, and previewed playlist creation, track addition, and exact track removal.
      MIT

    • 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
      4 npm
      MIT

    • Last.fm Taste MCP

      sptmru
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Last.fm listening analytics and recommendations by combining Last.fm and MusicBrainz metadata, maintaining a local listening index, and recording explicit preferences. Enables queries for listening summaries, taste profiles, artist context, and evidence-backed recommendations via MCP tools.
      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

    A4.1/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (listens, stats, metadata, feedback, pins, playlists, etc.). A few could be confused—e.g., get_user_stats vs get_activity_stats both deal with stats, and manage_recording_feedback vs manage_recommendation_feedback are similar—but the detailed descriptions and parameter sets make each tool's role clear enough to prevent misselection.

    Naming Consistency4/5

    The naming predominantly follows a consistent get_/manage_/submit_ pattern (get_listens, get_user_stats, manage_playlist, submit_listen). Exceptions like 'lb_radio' and 'generate_cover_art' break the pattern slightly, but they are still readable and self-explanatory. Overall, the conventions are predictable with a few outliers.

    Tool Count4/5

    At 37 tools, the surface is substantial, but it corresponds to a complete API wrapper for ListenBrainz. Each tool bundles multiple related endpoints (e.g., manage_playlist covers 9 actions), so the functional scope is well-managed. It sits at the high end of 'reasonable' for a full-featured service, not sprawling or redundant.

    Completeness5/5

    The tool set covers the major ListenBrainz domains: listening data (submit/get/manage), statistics (user/sitewide/activity), metadata lookup and mapping, recommendations and feedback, pins, follows, playlists (create/edit/delete/copy/export/import), feed and timeline events, cover art generation, and settings/status. It includes both read and write operations, and even handles edge cases like token validation and dump info. No obvious dead ends or missing lifecycle steps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources