flipper-ble-mcp
Related Servers
Alternatives to flipper-ble-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceTalk to your Flipper Zero from Claude Code — or any MCP client. Storage, app deployment, screen capture, button automation, JavaScript execution on the device, and honest answers about what is nearby.66MIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive a Flipper Zero over USB by capturing the screen as PNG, pressing buttons and navigating menus, running CLI commands, and managing files (list, read, download, MD5-verified upload, delete). It also lets agents launch apps, execute JavaScript and BadUSB scripts, transmit saved Sub-GHz signals, and query device status, firmware, and SD-card structure.32MIT
- AlicenseNot gradedqualityDmaintenanceControl a Govee BLE RGBIC LED strip from Claude (or any MCP client) over Bluetooth on macOS.MIT
- AlicenseNot gradedqualityDmaintenanceModular MCP server for interacting with a Flipper Zero from MCP-capable clients (including Claude Desktop). Supports system info, BadUSB scripts, and music playback over USB or WiFi.37MIT
- AlicenseNot gradedqualityBmaintenanceExposes 238 schema-typed tools over streamable-HTTP MCP that let a client drive a Flipper Zero, an AWOK Biscuit (ESP32-C5) and an ESP32 Marauder — scanning, screen mirroring, storage, and other device operations — from natural-language or direct tool calls. Transmit/attack tools stay behind an explicit human confirmation gate.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to control Nordic Thingy:52 IoT devices via Bluetooth LE, allowing users to manage LED colors, play sounds, and read environmental sensors through natural language conversations.-
TDQS
Scored across 38 tools
Each tool has a distinct purpose and clear boundaries. Even similar tools like 'press' and 'press_sequence' serve different needs (single vs batch). No two tools are easily confused.
Tools use a consistent snake_case pattern with verb_noun structure predominating. A few tools like 'playbook' and 'healthwatch' deviate but are descriptive and do not cause confusion.
38 tools is high but justifiable for comprehensive BLE device control covering storage, GPIO, apps, system, and specialized actions. However, some tools like 'selftest' and 'playbook' are meta and could be merged.
The tool set covers all major aspects of Flipper operation: storage CRUD, app lifecycle, GPIO, system info/control, and specialized actions (IR, Sub-GHz, BadUSB). No obvious gaps for the intended domain.