boss-katana-mcp
Related Servers
Alternatives to boss-katana-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables users to build and tweak BOSS GT-1 guitar tones and patches through plain-language conversation, with Claude writing amp, drive, and effect settings over USB. It can also listen to the pedal's audio, adjust levels and noise suppression, manage user slots, and run a metronome.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local AI agents to control a Fender Mustang GT40 through Fender Tone on Android, capture and compare USB recordings, and perform validated, bounded tone refinements without paid AI APIs.MIT
- AlicenseNot gradedqualityBmaintenanceLets AI assistants control a NUX MG-30 guitar processor over USB MIDI by picking amp, cab, drive, modulation, delay and reverb models, toggling blocks, and setting knobs by name. It can also read, save, rename, back up and restore presets on the device, and apply whole tone recipes from JSON patch files.36 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to control a Sonicake Pocket Master guitar processor over USB MIDI by describing tones in plain words — selecting amp/cab/effect models, setting parameters, reordering the signal chain, and saving, renaming, backing up or restoring presets. It also provides offline tools for inspecting firmware and rebuilding it with a translated UI, such as Russian.32 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to automatically discover and control supported laboratory instruments over USB, LAN, and serial connections, including power-supply output, setpoint, and protection management plus multimeter measurements.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control Ableton Live with full access to Live's object model, including clip creation, device control, automation, and audio signal capture for mixing and mastering tasks.1MIT
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes, but katana_launch and katana_connect overlap because launch can also connect, and katana_status slightly overlaps with katana_get around current patch/effect variation information. The descriptions mostly clarify when to use each, so an agent can usually choose correctly.
All tools use a consistent katana_ prefix followed by a short action-oriented name, such as katana_get, katana_set, and katana_list_params. The convention is predictable and readable throughout.
Six tools is well-scoped for a focused amp-control server: connection lifecycle, parameter discovery, read, write, and status. Each tool has a clear role, and there are no redundant extras.
The live-control workflow is covered from launch/connect through parameter discovery, read, and write, but katana_set explicitly edits only the live buffer and there is no tool to save the current tone to a patch. Patch switching or listing is also absent, which creates a notable dead end for persistence-oriented workflows.