{ "name": "My Device", "services": [ { "uuid": "180F", "primary": true, "characteristics": [ { "uuid": "2A19", "properties": ["read", "notify"], "value": "55", "format": "uint8" } ] } ] } ``` `properties` may contain: `read`, `write`, `writeWithoutResponse`, `notify`, `indicate`. `format` accepts the same values as `--format` in `read`/`write`: `hex` (default), `utf8`, `uint8`, `uint16le`, `uint32le`, `float32le`, `base64`, `raw`. **Examples:** ```sh # Advertise a name + service UUID (scanner-visible, no GATT characteristics) % blew periph adv -n "My Sensor" -S 180F # Multiple service UUIDs % blew periph adv -n "My Sensor" -S 180F -S 180A # Full GATT server from a config file % blew periph adv --config device.json # Config file with name override % blew periph adv -n "Override Name" --config device.json ``` Example config files are provided in the [`Examples/`](Examples/) directory: | File | Description | |------|-------------| | `health-thermometer.json` | Health Thermometer (`1809`) — indicate temperature measurement (2A1C), read temperature type (2A1D), read/write/notify measurement interval (2A21) | | `environmental-sensing.json` | Environmental Sensing (`181A`) — read/notify temperature (2A6E), humidity (2A6F), and pressure (2A6D) | | `blood-pressure.json` | Blood Pressure (`1810`) — indicate measurement (2A35), read feature flags (2A49) | | `custom-sensor.json` | Fully custom vendor service with 128-bit UUIDs — read/notify value, read/write config register, write-only command endpoint | **Output (text mode):** ``` Advertising "My Sensor" [180F (Battery Service)] Service 180F (Battery Service) +-- 2A19 (Battery Level) [read, notify] [12:34:56] central A1B2C3D4 connected [12:34:56] read 2A19 (Battery Level) by A1B2C3D4 [12:34:57] subscribe 2A19 (Battery Level) by A1B2C3D4 [12:35:01] write 2A19 (Battery Level) by A1B2C3D4 <- 2a ^C Stopped advertising. ``` **Output (kv mode):** ``` event=connected ts=12:34:56 central=A1B2C3D4-... event=read ts=12:34:56 central=A1B2C3D4-... char=2A19 event=subscribe ts=12:34:57 central=A1B2C3D4-... char=2A19 event=write ts=12:35:01 central=A1B2C3D4-... char=2A19 value=2a ``` #### `periph clone` — Clone a real device ``` blew periph clone [-n ] [-i ] [--save ] ``` Connects to a target device, discovers its full GATT tree, reads all readable characteristic values, disconnects, then starts advertising as a clone. | Flag | Description | |------|-------------| | `-n, --name` | Target device name filter. | | `-i, --id` | Target device identifier. | | `-o, --save ` | Save the cloned GATT structure to a JSON config file for later reuse. | **Clone scope:** - Cloned: advertised name, service UUIDs, full GATT structure, initial characteristic values (for readable characteristics). - Not cloned: manufacturer data, service data in ADV payload, ADV timing. **Examples:** ```sh % blew periph clone -n "Heart Rate Monitor" % blew periph clone -i F3C2A1B0-... --save hr-monitor.json ``` #### REPL-only periph commands In REPL and `exec` mode, `periph adv` and `periph clone` run in two phases. The startup phase (configure + start advertising) is synchronous and confirms the peripheral came up. Once advertising is confirmed, the event loop runs as a background task and the prompt is returned immediately. This makes `periph stop`, `periph set`, and `periph notify` usable in the same session: | Command | Description | |---------|-------------| | `periph stop` | Stop advertising and cancel the background event task. | | `periph set [-f ] ` | Update a characteristic's stored value. | | `periph notify [-f ] ` | Update value and push a notification to all subscribers. | | `periph status` | Show advertising state, service/characteristic counts, subscriber count. | ``` blew> periph adv --config device.json Advertising "My Device" [180F] Advertising in background. Use 'periph stop' to stop. blew> periph notify -f uint8 2A19 42 blew> periph stop Stopped advertising. ``` In `exec` mode the same non-blocking behaviour applies, enabling scripts like: ```sh % blew exec "periph adv -n 'My Device' --config device.json; periph set 2A19 ff; periph notify 2A19 ff" ``` --- ## MCP Server Mode `blew mcp` starts a [Model Context Protocol](https://modelcontextprotocol.io) server over stdio, exposing all BLE operations as individual MCP tools. AI agents (Cursor, Claude Desktop, etc.) can discover and invoke these tools to interact with BLE devices programmatically. The server is stateful: BLE connections and peripheral state persist across tool calls, just like the REPL. Tool results are returned as structured JSON (`structuredContent`), giving agents typed access to scan results, GATT data, read values, and more. ### Agent configuration **Cursor** (`.cursor/mcp.json`): ```json { "mcpServers": { "blew": { "command": "/path/to/blew", "args": ["mcp"] } } }

blew BLE MCP

Installation