春风元力千面 2 Pro MCP
Related Servers
Alternatives to 春风元力千面 2 Pro MCP
No user-submitted related servers found.
Related Servers
- 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.27BSD 2-Clause "Simplified"
- AlicenseAqualityFmaintenanceEnables MCP clients to control DG-Lab Coyote 2.0/3.0 devices via Bluetooth, providing tools for device scanning, connection, strength adjustment, wave design, and emergency stop.1430 npm13MIT
- AlicenseAqualityDmaintenanceA stateful Bluetooth Low Energy (BLE) MCP server that enables AI agents to scan, connect, read/write characteristics, and subscribe to notifications on BLE devices.3573 PyPI19MIT
- AlicenseBqualityCmaintenanceA lightweight Bluetooth Low Energy debug MCP server for AI agents. It provides 21 tools for BLE scanning, connection, GATT read/write, descriptor access, MTU query, notification subscription, device recon, and engine diagnostics.21Apache 2.0
- AlicenseBqualityCmaintenanceEnables natural-language control of DK-META2 devices through local BLE for vibration, linear extension, and rotation. It also supports scanning, connecting, status checks, and safe stop/disconnect operations without cloud access.82MIT
- AlicenseNot gradedqualityBmaintenanceProvides 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.50 PyPI13MIT
TDQS
Scored across 22 tools
Most tools map to a distinct resource+action: device lifecycle, per-actuator setters (suction/vibration/linear/rotary), stop commands, and waveform/recording lifecycles. The only real overlap cluster is stop_device vs stop_vibration (and set_suction vs set_vibration), but the descriptions explicitly disambiguate them by stating stop_device zeroes everything and that single-channel stop is unverified. Waveform creation has three entry points (sine, intent, custom save) but each is clearly scoped differently.
Nearly all tools follow a consistent snake_case verb_noun pattern (list_devices, connect_device, set_suction, create_sine_waveform, start_action_recording). Minor deviation: the recording lifecycle is named 'action_recording' in three tools but shortened to 'recording' in save_recording_as_waveform, and create_sine_waveform/create_intent_waveform embed an adjective mid-name. Readable and predictable overall.
22 tools is on the heavy side for a BLE device controller. Several per-channel setters (set_suction/set_vibration/set_linear/set_rotary) and three separate waveform-creation tools could plausibly be collapsed into generic parameterized tools, suggesting some surface bloat. The count is not absurd given multi-device and recording support, but it is borderline.
Strong coverage: device scan/connect/disconnect/status, per-channel actuator control, global stop, full waveform create/list/get/start/stop/status, and a complete recording start/stop/get/save-as-waveform cycle. The notable gap is waveform management — no delete_waveform or rename, so stored waveforms accumulate with no cleanup path. Minor: no per-device capability/model query beyond the scan annotation.