Skip to main content
Glama
labelgrid

LabelGrid MCP Server

Official
by labelgrid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to LabelGrid MCP Server

No user-submitted related servers found.

    Related Servers

    • Discogs MCP Server

      davidmsawyer
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for interacting with Discogs music collections. It enables AI assistants to search, manage, and analyze personal music libraries with OAuth authentication and intelligent features like mood mapping.
      MIT

    • lacuna-mcp

      JOYLINK-LTD
      A
      license
      Not graded
      quality
      B
      maintenance
      Official MCP server for the Lacuna Music API. Generate AI music — full songs with vocals and lyrics, or instrumentals — with style prompts, task status polling, and audio downloads.
      4
      MIT

    • beatport-mcp-server

      ivo-toby
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides access to the Beatport API for music discovery and data retrieval, enabling users to search for tracks, artists, labels, releases, and charts through natural language.
      4
      MIT

    • lidarr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Lidarr's full v1 REST API as tools for reading and managing artists, albums, tracks, queue, history, and more. It enables LLMs to interact with a Lidarr instance via natural language.
      15
      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.8/5.0

    Scored across 84 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_artist, get_release, list_review_issues). Even with many list/get tools, their parameters and purposes are clearly differentiated. No two tools appear to do the same thing.

    Naming Consistency5/5

    The vast majority use the verb_noun snake_case pattern (create_, get_, list_, update_, delete_, upload_, download_). Minor exceptions like 'setup' and 'takedown_release' are still understandable and do not break the pattern significantly.

    Tool Count2/5

    With 84 tools, the server is over-scoped for typical use. While the domain is complex, this many tools can confuse an agent and increase surface area unnecessarily. A more focused set would improve coherence.

    Completeness5/5

    The tool set covers the full lifecycle for artists, labels, releases, tracks, licenses, webhooks, etc. It includes creation, retrieval, update, deletion, upload/download, validation, distribution, and analytics. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources