A
licenseD
qualityD
maintenanceA Model Context Protocol server that allows AI assistants like Claude and Cursor to create music and control Sonic Pi programmatically through OSC messages.
2
20 npm
18
MIT
sonic-mcp
by AJBogo9
Related Servers
Alternatives to sonic-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude to FL Studio, allowing the AI to compose music, control instruments, and live record melodies, chords, and drums to the piano roll.105-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects Claude to FL Studio, enabling natural language control of transport, mixer, channel rack, and piano roll operations.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes a synthesizer composer's command catalog as tools, enabling Claude to compose, sound-design, and mix in a live browser session.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude to FL Studio, allowing the AI to send melodies, chords, and drum patterns directly to the DAW via virtual MIDI ports.55-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants like Claude to interact with FL Studio's piano roll, allowing users to create melodies, chord progressions, and musical patterns through natural language with automatic, real-time updates.38MIT
TDQS
A3.8/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a specific action or resource with minimal overlap. For example, run_code and run_in_buffer are differentiated by buffer slot, and load/save tools are separated by pattern vs song. The mixer tools are clearly distinct by filter type and action.
Naming Consistency4/5
Most tools follow a verb_noun pattern (e.g., list_patterns, save_song). The mixer_* tools use a consistent noun_prefix + verb pattern, and record_start/stop are symmetrical. Ping stands alone but is a common convention.
Tool Count4/5
21 tools cover the full range of Sonic Pi interactions without feeling excessive. The count is slightly high but justified by the need for separate loading, saving, mixing, and recording functions.
Completeness5/5
The tool set covers all major workflows: code execution (run_code, run_in_buffer), library management (list/load/save patterns and songs), audio control (mixer, volume, stop_all), recording, debugging (get_log), and sync (send_cue). No obvious gaps for typical usage.
Maintenance
ActivityInactive
ResponsivenessNo issues