Skip to main content
Glama
Sign In
doricomcp

doricomcp

by kulbiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to doricomcp

No user-submitted related servers found.

    Related Servers

    • musescore-mcp

      strongbeen04
      F
      license
      A
      quality
      D
      maintenance
      Enables Claude AI to convert, edit, and analyze MuseScore files (.mscz, .musicxml, MIDI) through natural language commands, supporting format conversion, transposition, harmony analysis, and more.
      20
      1
      -

    • leadsheet

      Niraj-Kamdar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to compose real music from chord-symbol descriptions into MIDI files and audio previews, with musicology cross-checks on every chord.
      1
      AGPL 3.0

    • fl-mcp-2026

      emmggew-svg
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Desktop to drive FL Studio 2025 and 2026 through natural language, diagnosing and repairing mixes, configuring plugins, writing notes and chords in any scale, exporting arrangements to MIDI, and analyzing audio for tempo, key, and melody.
      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

    C2.7/5.0

    Scored across 66 tools

    Disambiguation3/5

    Most tools have a clear verb+object purpose (add_notes, read_markings, set_tempo), but several overlap: add_span vs add_hairpin both create hairpins, add_articulation vs add_note_marking (kind=articulation) both add articulations, and delete_range vs delete_events both remove content. set_property and run_command are generic catch-alls that could do almost anything, though the descriptions do explicitly point to the specialised tool ('for exact positions use add_hairpin'), which keeps misselection recoverable rather than fatal.

    Naming Consistency4/5

    The dominant pattern is verb_noun (add_player, get_score_overview, read_music, delete_flow, set_pitch), applied consistently across the large write surface. Deviations are limited to a few noun_verb tools (dialog_click, dialog_set, layout_flows, score_changes) and bare-verb transport tools (play, stop, undo, redo, refresh, screenshot), which are conventional enough not to break predictability.

    Tool Count2/5

    66 tools is far beyond what an agent can comfortably scan and choose from in one surface, even for a rich domain like score engraving. The set is really several servers in one (transport/undo, accessors, music reading, note writing, markings, dialogs, house style), and should have been grouped or narrowed.

    Completeness4/5

    Coverage is unusually thorough: status/diagnostics, structure (players, flows, layouts), reads (music, markings, context, bar map, changes), note and marking writes, options, dialogs and an escape hatch, plus undo/redo. Minor gaps remain — no remove_player or delete_layout (removal exists for instruments and flows only), no transpose/bulk pitch-shift beyond edit_notes, and no way to read back a layout's flows (layout_flows is write-only).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources