DG-MCP
Related Servers
Alternatives to DG-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables natural-language control of DG-LAB Coyote V2/V3 hardware from any MCP client, with QR pairing, real-time telemetry, waveform playback, and built-in safety limits.116 npmGPL 3.0
- FlicenseAqualityBmaintenanceEnables Claude or any MCP client to design and print text and images to Bluetooth thermal label printers, including scanning, configuring, and managing multiple printers.12-
- AlicenseNot gradedqualityDmaintenanceBluetooth Low Energy (BLE) MCP server that allows AI agents to scan, connect to and communicated with BLE devices, as well as simulate BLE perhipherals.18BSD 2-Clause "Simplified"
- AlicenseNot gradedqualityAmaintenanceProvides a local MCP server for Bluetooth Low Energy automation, enabling scanning, GATT inspection, characteristic reads and writes, and evidence capture, diff, and replay with safety guards.40 PyPI10MIT
- AlicenseNot gradedqualityCmaintenanceEnables tracking and monitoring of Capillus Bluetooth caps for treatment sessions, adherence, and device status using local BLE data, without requiring cloud APIs.MIT
- AlicenseAqualityCmaintenanceA stateful Bluetooth Low Energy (BLE) MCP server that enables AI agents to scan, connect, read/write characteristics, and subscribe to notifications on BLE devices.3518MIT
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose with no overlap. For example, adjust_strength is for gradual intensity changes, burst for short pulses, and change_wave for waveform changes, all with explicit triggers and constraints. Start, stop, and emergency_stop are also well-separated.
Most names follow a consistent verb_noun pattern with underscores (e.g., adjust_strength, change_wave, list_waveforms). The only minor deviation is 'burst', which is a single verb, but this is a clear exception and does not cause confusion.
14 tools is well-scoped for controlling a Coyote device. The count covers connection management, scanning, waveform manipulation, intensity control, and a timer, with no superfluous tools.
The tool surface covers the full lifecycle: connection (connect/disconnect/scan), operation (start/stop/adjust_strength/burst/change_wave), waveform management (list_waveforms/load_waveforms/design_wave), status (get_status), safety (emergency_stop), and even a timer for deferred interactions. No obvious gaps for the domain.