Skip to main content
Glama
Turbotailz

lexicon-mcp

by Turbotailz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to lexicon-mcp

No user-submitted related servers found.

    Related Servers

    • lexicon-mcp

      zanda-msingi
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-aware AI clients to read, query, and modify a Lexicon DJ library through structured tool calls, including searching tracks, managing tags, and curating playlists or smartlists.
      13
      MIT

    • engine-dj-mcp

      Venut-Technologies
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to query and manage a local Engine DJ library on macOS, including searching tracks by BPM, key, genre, or comments, auditing duplicates and missing files, reading cues and beatgrids, and building playlists or fixing tags when write access is enabled.
      9
      218 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.
      -

    • library

      shadowroommusic
      A
      license
      A
      quality
      C
      maintenance
      Manages a local SQLite music track library with fingerprint-based incremental scanning, multi-condition search, missing analysis completion, and crate management, enabling DJs to organize and retrieve tracks without moving files.
      13
      AGPL 3.0
    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.6/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clear distinct purposes (ping, list, get, update, search, control, player status). However, lexicon_request and lexicon_raw_request are redundant, and lexicon_control is a catch-all that could overlap with other specific actions.

    Naming Consistency5/5

    All tools follow a consistent 'lexicon_verb_noun' pattern using snake_case. The deprecated raw_request is slightly irregular but clearly marked.

    Tool Count5/5

    15 tools cover a comprehensive set of operations for a DJ library management API without being overwhelming or too sparse.

    Completeness4/5

    Core operations for tracks, playlists, library stats, and player state are covered. A generic 'request' endpoint fills gaps, but explicit create/delete for playlists is missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources