| 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
connect using the address from the scan results.
- Exploration: Call
services to list available GATT services and characteristics.
- Interaction: Use
read for one-time values, write_request/write_command to send data, or notify/indicate + get_notifications + unsubscribe for streaming data.
- Cleanup: Always call
disconnect when 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) and data_utf8 (convenience field). If the data is not valid UTF-8, invalid bytes are skipped, so data_utf8 may be incomplete or empty. Use data_hex for protocol analysis and data_utf8 for human-readable strings.
- Notifications/Indications: Use
notify or indicate to subscribe, get_notifications to retrieve buffered data, and unsubscribe when done.
- Bluetooth Status: Assume Bluetooth is enabled by default. Only check
bluetooth_enabled when an operation fails.
Additional Resources
