name: simpleaible description: Use the SimpleAIBLE MCP server to scan, connect, and interact with Bluetooth devices. This skill provides guidance on the recommended flow (scan -> connect -> services -> read/notify) and handles platform-specific differences like UUIDs on macOS vs MAC addresses on Linux. Use when the user wants to interact with BLE hardware or debug Bluetooth connections.
SimpleAIBLE
SimpleAIBLE is an AI-friendly BLE toolkit powered by SimpleBLE. This skill provides instructions for using the SimpleAIBLE MCP server to interact with Bluetooth Low Energy (BLE) devices directly from the host machine.
Quick Start Flow
Always follow this sequence for BLE interactions:
- Scanning: Call
scan_for(default 5s) to find nearby peripherals. - Connection: Call
connectusing theaddressfrom the scan results. - Exploration: Call
servicesto list available GATT services and characteristics. - Interaction: Use
readfor one-time values,write_request/write_commandto send data, ornotify/indicate+get_notifications+unsubscribefor streaming data. - Cleanup: Always call
disconnectwhen finished to release the device.
Core Instructions
- Scanning: Prefer scanning immediately before connecting to ensure the device is in the internal cache.
- Addressing: Be aware that macOS/iOS uses UUIDs for addresses, while Linux/Windows uses MAC addresses.
- Data Handling: Binary data is returned as
data_hex(always reliable) anddata_utf8(convenience field). If the data is not valid UTF-8, invalid bytes are skipped, sodata_utf8may be incomplete or empty. Usedata_hexfor protocol analysis anddata_utf8for human-readable strings. - Notifications/Indications: Use
notifyorindicateto subscribe,get_notificationsto retrieve buffered data, andunsubscribewhen done. - Bluetooth Status: Assume Bluetooth is enabled by default. Only check
bluetooth_enabledwhen an operation fails.
Additional Resources
- For detailed tool documentation and platform notes, see the reference guide.
- For concrete usage examples, see examples.md.
- For troubleshooting common issues, see troubleshooting.md.