A
licenseA
qualityD
maintenanceEnables conversational live coding with Claude AI and TidalCycles, allowing users to create and manipulate algorithmic music patterns through natural language.
7
17
MIT
tidal-cycles-mcp-server
by vinterstum
Related Servers
Alternatives to tidal-cycles-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects Claude Code to SuperCollider for AI-driven music composition, supporting real-time playback and non-realtime audio rendering at 50-150x realtime speed.MIT
- FlicenseNot gradedqualityCmaintenanceEnables Claude AI to control Ableton Live and Max for Live, allowing music production tasks like track management, MIDI editing, and pattern generation directly from conversation.-
- FlicenseNot gradedqualityBmaintenanceControl Ableton Live using natural language via Claude Code, with music theory engine for progressions, project persistence, and song cloning.-
- FlicenseAqualityDmaintenanceEnables natural language control of Pure Data patches through Claude AI, allowing dynamic creation, modification, and DSP control via the Model Context Protocol.1123-
- AlicenseNot gradedqualityBmaintenanceTwo-mode creative music studio for AI: scored composition (ABC notation with sheet music) and live performance (Strudel live coding with TidalCycles), with interactive UI rendering inline in Claude Desktop and other MCP clients.168 npm70MIT
TDQS
A4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool targets a clearly distinct action: evaluating patterns, stopping all/specific channels, querying state, soloing/unsoloing, and retrieving history or sample lists. The only potential overlap is hush vs. silence, but their descriptions make the all-vs-single-channel distinction unambiguous.
Naming Consistency5/5
All tools share the tidal_ prefix and use a consistent snake_case imperative style. Queries are uniformly get_ prefixed, and action verbs (eval, hush, silence, solo, unsolo) are simple and predictable.
Tool Count5/5
Eight tools is well-scoped for a TidalCycles live-coding server. Each tool serves a distinct part of the workflow without redundancy or unnecessary bloat.
Completeness4/5
The set covers the core live-coding lifecycle:play, stop, silence, solo, state inspection, history, and sample discovery. A minor gap is the lack of tempo/global control tools, but these may be outside the intended server scope.
Maintenance
ActivityInactive
ResponsivenessNo issues