Bluetooth Low Energy (BLE) MCP Server

Mac OS X command line BLE tool and MCP server

Local serverstdio

What is the Bluetooth Low Energy (BLE) MCP server?

Connect Bluetooth Low Energy (BLE) to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Mac OS X command line BLE tool and MCP server. The bluetooth low energy (ble) mcp server is what makes that connection.

What the server does

Stop fumbling with GUI apps to debug Bluetooth Low Energy devices. blew gives you full BLE control from the macOS command line: scan the airwaves, drill into any device's GATT tree, read and write characteristics, stream live notifications, and even spin up a virtual peripheral that other devices can connect to.

  • One tool, zero ceremony. — Scan, connect, inspect, read, write, subscribe -- each is a single command. Auto-connect means you never have to manually pair before doing real work
  • Interactive when you want it. — Launch the REPL for an exploratory session with tab completion, persistent history, and background subscriptions that print while you keep typing
  • Scriptable when you need it. — Chain commands with exec, pipe machine-readable kv output into awk or a log file, and use deterministic exit codes in CI or monitoring scripts
  • Full GATT visibility. — Print the service/characteristic tree of any device in one shot. Read all values inline. Look up any Bluetooth SIG characteristic's field-level spec without even connecting
  • Peripheral mode. — Turn your Mac into a virtual BLE device. Define a GATT server from a JSON config, or clone a real device's entire service tree and replay it
  • Human-readable by default. — Standard Bluetooth SIG UUIDs are resolved to their names everywhere -- scan results, GATT trees, notifications -- sourced from the official Bluetooth SIG database

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • disconnect — Disconnect
  • status — Show connection status
  • help — Show available commands
  • Homebrew — The Homebrew tool exposed by this server
  • Requirements — The MCP server (the blew mcp subcommand) depends on the MCP swift-sdk, which requires the Swift 6.1 toolchain (Xcode 16.3+). To keep blew building on

Credentials and setup notes

  • macOS 14 (Sonoma) or later - Xcode 16 or later (Swift 6.0+ toolchain) The MCP server (the blew mcp subcommand) depends on the MCP swift-sdk, which requires the Swift 6.1 toolchain (Xcode 16.3+). To keep blew building on older toolchains, MCP support is compiled in conditionally: when built with Swift 6.1 or newer the mcp subcommand is available; when built with Swift 6.0.x (Xcode 16.0–16.2)

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bluetooth Low Energy (BLE)'s toolset — disconnect, status, help and 2 more — is a fair guide to whether it matches your workflow. It is maintained by stass; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
disconnectDisconnect
statusShow connection status
helpShow available commands
HomebrewThe Homebrew tool exposed by this server.
RequirementsThe MCP server (the blew mcp subcommand) depends on the MCP swift-sdk, which requires the Swift 6.1 toolchain (Xcode 16.3+). To keep blew building on older toolchains, MCP support is compiled in conditionally: when built

Configuration

  • macOS 14 (Sonoma) or later - Xcode 16 or later (Swift 6.0+ toolchain) The MCP server (the blew mcp subcommand) depends on the MCP swift-sdk, which requires the Swift 6.1 toolchain (Xcode 16.3+). To keep blew building on older toolchains, MCP support is compiled in conditionally: when built with Swift 6.1 or newer the mcp subcommand is available; when built with Swift 6.0.x (Xcode 16.0–16.2)

Example prompts to try

  • Use Bluetooth Low Energy (BLE) to disconnect.
  • Use Bluetooth Low Energy (BLE) to status.
  • Use Bluetooth Low Energy (BLE) to help.

Frequently asked questions

It connects Bluetooth Low Energy (BLE) to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (disconnect, status, help, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Bluetooth Low Energy (BLE) directly.