Skip to main content
Glama
zas

MusicBrainz MCP Server

by zas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MusicBrainz MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-musicbrainz

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching music artists and releases, and retrieving artist biographies, discographies, release track listings, credits, and metadata through the MusicBrainz API.
      1 npm
      MIT

    • mcp-bookbrainz

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to BookBrainz open book metadata, enabling search, lookup, and browsing of works, editions, authors, publishers, and series via natural language or direct tool calls.
      167 npm
      MIT

    • music-mcp-agent

      thelma-tertrais
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables music search, metadata retrieval, local audio analysis (tempo, key, energy), recommendations, song recognition, and classical work resolution via Spotify, Last.fm, AudD, MusicBrainz, and Songkick APIs.
      -

    • mcp-discogs

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying music discography data from Discogs, including master releases, artist profiles, and label information.
      1 npm
      MIT

    • Discogs MCP Server

      donnatto
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, manage, and analyze personal Discogs music collections with features like mood-based recommendations, advanced search, and collection analytics.
      4 npm
      MIT

    • Luminous MCP Server

      esoltys
      F
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to a local music library for full-text search and filtering of tracks, albums, artists, genres, composers, and lyrics, plus listening analytics and metadata hygiene audits. Also lets users generate and populate playlists and control playback (play, pause, seek, volume) in a running player instance.
      -
    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.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between search_entities, search_artists, and search_releases that could cause confusion. The descriptions help clarify when to use each, but an agent might misselect between them for simple searches. Other tools like get_album_tracks vs get_release_details are well-differentiated with clear guidance.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as browse_entities, get_artist_details, search_artists, and lookup_by_barcode. All tools use snake_case with clear, descriptive names, making the set predictable and easy to navigate.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for the comprehensive MusicBrainz domain, covering entities like artists, releases, recordings, and labels. It includes essential operations like search, get details, and browse, though it might feel a bit heavy compared to simpler servers.

    Completeness5/5

    The tool set provides complete coverage for the MusicBrainz domain, including search, retrieval, and browsing across all entity types (artists, releases, recordings, labels, works, areas). It handles CRUD-like operations where applicable (e.g., get details, search) and includes niche tools like get_cover_art_urls and lookup_by_barcode, leaving no obvious gaps for agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources