flipper-ble-mcp
The flipper-ble-mcp server provides 38 tools to wirelessly control a Flipper Zero over Bluetooth LE, spanning device info, UI navigation, file management, app control, RF/IR transmission, GPIO, BadUSB, and health monitoring.
Device Info & Diagnostics
Read firmware, hardware, battery/power stats, real-time clock, and 60+ device fields
Ping for BLE liveness, scan for BLE advertising, run daemon self-tests
Retrieve an internal playbook/operating manual (recommended first call in a session)
Screen & Navigation
Capture the 128×64 display as a PNG screenshot over BLE
Inject single or sequential button presses (up/down/left/right/ok/back), with optional post-press screenshot
Storage & File Management
List, read, write, stat, rename, delete, and create directories on SD or internal storage
Compute MD5 checksums, check free/total space, and retrieve the most recently saved file in a folder (e.g., latest NFC scan or Sub-GHz capture)
App Control
Launch apps by name (optionally opening a file directly), exit the current app, check if an app is running
Load saved files into a running app, press named in-app buttons, and retrieve app error messages
RF/IR Transmission ⚠️ (gated, human approval required)
Transmit saved Sub-GHz captures via the app-driven TX path
Open saved IR remote files and trigger button presses to fire IR signals
GPIO
Read, write, and set pin modes (input/output) on supported GPIO pins
BadUSB / HID Injection ⚠️ (gated, human approval required)
Upload and execute DuckyScript payloads, injecting keystrokes into the USB-connected host
System Operations
Set the Flipper's date/time, check and clear the desktop swipe-lock, locate the device via beep/flash, and reboot in OS, DFU, or UPDATE mode
Health Monitoring
Run a scheduled read-only health poller (battery, storage, clock, firmware) that fires macOS notifications on anomalies; toggled on/off or run on-demand
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@flipper-ble-mcp screenshot my Flipper"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
flipper-ble-mcp 🐬📡
Drive a Flipper Zero wirelessly over Bluetooth LE from Claude — no USB cable — backed by a self-evolving knowledge base that makes every session faster than the last.
flipper-ble-mcp is three layers that form a loop:
An MCP server (
src/) — 38 tools that control a Flipper Zero over BLE: read device info & files, screenshot the screen, inject button presses, launch apps, app-driven Sub-GHz/IR transmit, GPIO, BadUSB, and a scheduled read-only health-watch.A skill (
.claude/skills/flipper/) — the operating brain: anORIENT → EXECUTE → CAPTUREloop, a routine index (task → KB doc → tools), verified menu maps, and safety gates.A knowledge base (the docs in this repo) — ships prebuilt with deep Flipper + toolkit knowledge the agent reads before acting and writes back to after (
/flipper-learn).
read the KB → act via MCP → capture what you learned → KB grows → next session is fasterThat last arrow is the point: instead of re-deriving how the device behaves each time, the agent accumulates expertise — and it ships with a big head start.
⚠️ macOS only (today). The Bluetooth work runs inside a small ad-hoc-signed
.appthat carries the macOS Bluetooth entitlement; the MCP process itself never touches BT. See Architecture.⚠️ Dual-use tool. It can transmit RF/IR and inject USB keystrokes (BadUSB). Your own devices, authorized targets, and legal frequencies only. Every real action is human-approved per call. See SECURITY.md.
Why
LLM agents are great at reasoning and terrible at remembering what they learned last time. This project pairs real hardware control (an MCP server) with a knowledge base the agent both consumes and grows — so operating a Flipper gets faster and more reliable with use, and the knowledge is portable (it ships in the repo, not trapped in one chat).
Related MCP server: Flipper Zero MCP Server
Demo
Demo GIF coming soon.
Architecture
Claude (Desktop / Code)
│ MCP (stdio)
▼
flipper-ble MCP server ──────────────┐ (never touches Bluetooth directly)
│ token-authed Unix socket │
▼ │
resident daemon (holds ONE BLE link) │ runs inside FlipperBLE.app —
│ Bluetooth LE │ the ad-hoc-signed bundle that carries
▼ ┘ the macOS Bluetooth (TCC) entitlement
Flipper ZeroA persistent daemon keeps a single BLE connection open (status/reads ~0.1–0.3 s, screenshot/press
~1.5 s; idle-disconnects to free the radio for your phone). The socket is 0600 + shared-token authed.
Install
Prerequisites: macOS, a Flipper Zero (Momentum / Unleashed / official firmware), Claude Code or Claude Desktop, Python 3.11+, and
uv.
git clone https://github.com/pogorelov-labs/flipper-ble-mcp && cd flipper-ble-mcp
python3 -m venv .venv && .venv/bin/pip install -e . # bleak, protobuf, mcp + the package
./app/build_app.sh .venv/bin/python # build + ad-hoc-sign the Bluetooth helper (one-time)Add the MCP server to Claude — claude mcp add flipper-ble -- uvx flipper-ble-mcp, or in your Claude Desktop config:
{
"mcpServers": {
"flipper-ble": { "command": "uvx", "args": ["flipper-ble-mcp"] }
}
}Then run Claude Code in this repo: the flipper skill + the KB are auto-discovered, so just ask —
"what's my Flipper's battery?" / "screenshot my Flipper." (To use the skill outside the repo, copy
.claude/skills/flipper/ and .claude/commands/flipper-learn.md into your ~/.claude/.)
The self-evolving knowledge base
Seed (this repo) — curated, general Flipper + toolkit knowledge. Indexed by
llms.txt.Local overlay (
kb-local/, git-ignored) — where each install's new learnings land via/flipper-learn. The skill reads it alongside the seed; local entries win on conflict.PR-back — broadly-useful learnings get promoted into the seed via pull request, so the community's collective experience compounds. Classification rule:
.claude/skills/flipper/references/kb-map.md.
Tools
38 tools — full table + RPC mapping in resources/flipper-ble-control.md. Highlights: device_info, power_info, screenshot, press / press_sequence, storage_*, app_launch, transmit_subghz / transmit_infrared (gated), gpio_*, run_badusb (gated), healthwatch.
Safety & responsible use
See SECURITY.md: every action is human-approved per call; RF/IR/BadUSB is for your own authorized targets on legal bands; the health-watch is read-only and default-off; the agent is instructed never to autonomously transmit.
Contributing
See CONTRIBUTING.md — including how to PR a learned-KB entry back into the seed.
House style for KB docs: CLAUDE.md.
License
MIT © 2026 Ruslan Pogorelov.
State: 70 content docs, ~102k words. The knowledge base below is generated from per-doc frontmatter —
run python3 build-kb-index.py to rebuild; never hand-edit the block.
Index
Start here / Core
File | Status | What's in it |
✅ | Scored data model — schema + 1–10 real-use rubric + 63 use-cases in ranked score bands. | |
✅ | Hardware block map, STM32WB MCU, radios, software stack, SD layout, and full capability map. | |
✅ | Dual-use ground rules — RF-transmit, cloning, HID, EMV reality, and a responsible-use checklist. | |
✅ | One-line definitions of every term used across the KB, each linking to its deep-dive. |
Dataset: use-cases.csv / use-cases.json — regenerate the JSON with
python3 build-use-cases-json.py. UC-ID → docs map: uc-index.json.
Firmware
File | Status | What's in it |
✅ | Firmware comparison matrix, Xtreme to Momentum history, flashing/recovery, and legal/stability risks. | |
✅ | Step-by-step — back up SD, flash Momentum, restore, re-enable add-ons, verify (frontier Stage 0). | |
✅ | Feature-rich Xtreme successor — capabilities by domain plus an honest is-it-the-best verdict. | |
✅ | Stock OFW from Flipper Devices — abilities, deliberate limits, and the sanctioned app catalog. | |
✅ | Kitchen-sink, bleeding-edge custom firmware with the largest bundled app/game set and most crashes. | |
✅ | Unlocked, stable, RF-focused custom firmware — the oldest OFW fork, favored for serious Sub-GHz work. |
Hardware & GPIO
File | Status | What's in it |
✅ | GPIO pinout, ADC/PWM/buses, power limits, and the Flipper's internal-radio front-end hardware. | |
✅ | Bruce vs Ghost ESP vs Marauder — which firmware to flash on an ESP32 Flipper backpack. | |
✅ | The ESP32-WROOM Marauder backpack hardware — GPIO 9-18 mount (3V3), the freeze fix, BOOT/RST buttons, dual-SD, flashing. | |
✅ | Current GPIO add-ons — DevBoard, VGM, Marauder/Ghost ESP, Mayhem, NRF24, CC1101, GPS, protoboards. | |
✅ | Which GPIO add-on(s) to buy, by goal/persona, with a board-vs-persona comparison table. | |
✅ | Plain-words use-cases + pros/cons for each Flipper GPIO add-on — GPS, NRF24, CC1101, BLE sniffer, thermal, geiger. | |
✅ | DIY GPIO add-ons — I²C/SPI/UART sensors, displays, LoRa, BLE sniffer, logic analyzer, and design limits. |
Capabilities (built-in feature deep-dives)
File | Status | What's in it |
✅ | HID keystroke injection over USB (and BLE on CFW) — Ducky Script, layouts, OS targets, and blue-team defenses. | |
✅ | Dallas / Cyfral / Metakom contact "touch" keys over 1-Wire — read, emulate, and clone to writable blanks. | |
✅ | Capture, store, and replay consumer IR; protocols, .ir format, universal remotes, and the Flipper-IRDB library. | |
✅ | Overview of the two card radios — LF 125 kHz RFID and HF 13.56 MHz NFC; deep dives live in cards/. | |
✅ | CC1101 sub-1-GHz radio — bands, modulation/presets, on-device workflows, .sub format, protocol decoders. |
Cards, NFC & RFID (deep-research sub-domain)
File | Status | What's in it |
✅ | Hub: card taxonomy, security tiers, and the cards doc index | |
✅ | What's cloneable + how, magic cards, and a blanks list | |
✅ | iCLASS legacy vs SE/SEOS; the PicoPass app | |
✅ | EM4100/HID Prox/Indala/AWID + T5577 cloning | |
✅ | MIFARE Classic/Ultralight/NTAG/DESFire + Crypto1 attacks | |
✅ | RFID/NFC physics + ISO 14443/15693/18092 protocols |
Wi-Fi (ESP32 Marauder add-on)
File | Status | What's in it |
✅ | Hub: Wi-Fi capability map — which use-case lives in which doc. | |
✅ | Rogue-AP captive-portal credential harvesting. | |
✅ | Agent-driven AP scan — launch Marauder over the BLE MCP, run scanap, read the full network list from the SD log. | |
✅ | Runnable: audit your own PSK (capture, hcxtools, hashcat). | |
✅ | Deauthentication: the 802.11 flaw and the PMF/802.11w defense. | |
✅ | Scan, sniff to PCAP, beacon spam, analyzer, wardrive, detect-deauth. | |
✅ | Capture the WPA 4-way handshake / PMKID and crack it offline with hashcat. |
Bluetooth / BLE
File | Status | What's in it |
✅ | Hub for Bluetooth on this rig — Classic vs BLE, and the BLE use-case map across the sub-domain docs. | |
✅ | How Find My works, anti-stalking tracker detection, rig limits, and FindMy Flipper as the inverse emulator. | |
✅ | Real BLE connection capture via nRF52840/nRF Sniffer or Sniffle, plus crackle for LE Legacy pairings. | |
✅ | Advertising-flood pairing popups (Sour Apple/Fast Pair/Swift Pair); the iOS 17.2 story; nuisance, not a hack. | |
✅ | Bluetooth Classic (BR/EDR) attacks — KNOB, BIAS, BlueBorne — and why this rig can't touch them. | |
✅ | Interception reality — advertising vs connection sniffing, pairing crypto, and what this rig can/can't do. |
Theory
File | Status | What's in it |
✅ | The attack class that beats correct crypto — PKES/BLE/NFC relay; UWB/distance-bounding defense | |
✅ | KeeLoq internals, RollJam/RollBack, cryptanalysis, and defenses | |
✅ | The gap no patch closes — phishing, BadUSB social-eng, NFC/QR baiting; passkeys as the fix |
Topics
File | Status | What's in it |
✅ | What an AI agent driving the Flipper unlocks, the hardware/crypto ceiling, and injection→hardware risk. | |
✅ | Maker/electronics projects, FAP/ufbt app dev, on-device JavaScript, and asset packs. | |
✅ | Honest red-team framing — capability-vs-tool matrix, methodology, ROE checklist, remediation. | |
✅ | How Flipper's Sub-GHz region provisioning works, why "Missing region file" blocks TX, and the fix. | |
✅ | Legitimate uses & project ideas organized by capability, with a starter-projects table. | |
✅ | Where capability still beats modern defenses in 2026 — deployment inertia, relay attacks, IoT floor, FM11RF08S. |
Resources
File | Status | What's in it |
✅ | Curated GitHub repos by category, with maintenance flags | |
✅ | Discord/Reddit/forums + vetted YouTube creators | |
✅ | Wireless Flipper control SOLVED — read/see/drive/launch/file-read over BLE via the flipper-ble MCP server. | |
✅ | Fun/novel projects — FlipperHTTP web apps, games, VGM DOOM, MagSpoof, Home Assistant | |
✅ | Drive the Flipper from Claude — MCP servers, AgentFlipper, Mac/USB setup, AI-control risks | |
✅ | How an AI agent should drive the Flipper via the MCP toolkit — data-first algorithm, menu maps, app-entry recipes, conventions. | |
✅ | Gated control MCP server (Stage 3) — 14 tools (input/apps/LED/GPIO/IR+SubGHz-TX/writes + screenshot) over USB, each approved. | |
✅ | Gated, default-off launchd job that polls the Flipper read-only 3×/day (battery/storage/clock/firmware) and notifies on anomalies. | |
✅ | The read-only MCP server we built for this rig — 14 native mcp__flipper__* device-read tools over USB, one allowlist. | |
✅ | Leaderboard + people — top repos by stars, devs/orgs to follow, the ESP32 scene | |
✅ | Runbook for the BadUSB/HID, CAN/automotive, physical-access, crypto and misc security FAPs on my Momentum rig. | |
✅ | Per-app runbook for the LF RFID (125 kHz), iButton/1-Wire, and Infrared apps on the owner's maxed Momentum rig. | |
✅ | Per-app reference for every 13.56 MHz NFC .fap on my Momentum rig — what it does, options, gotchas, sources. | |
✅ | Docs, cheat-sheets, and deep RF+NFC learning material by level | |
✅ | Deeper cut — pyFlipper scripting, sensor/utility apps, data/dumps, asset packs, 3D | |
✅ | Install busse MCP, add to Claude Code over USB, scope it read-only with gating — first safe AI↔device milestone. | |
✅ | Per-app reference for the Sub-GHz/RF .faps on this Momentum rig — what each does, key options, use-cases, gotchas, sources. | |
✅ | Device-specific Sub-GHz repos and .sub collections (TouchTunes, gates, Tesla, sensors) | |
✅ | qFlipper, Flipper Lab, flashers, and an SD-backup checklist | |
✅ | Per-app runbook for the ESP32 / BLE / NRF24 companion FAPs on my Momentum rig — what each does, settings, hardware, sources. |
Available Tools
38 toolsapp_buttonA
Press a NAMED in-app button over BLE (app_button_press + release). App-specific: in the universal IR / Sub-GHz / etc. apps this triggers actions (including transmit). args = the button name/index the running app expects. ⚠️ Advanced + app-specific; YOUR OWN TARGETS ONLY. Real action.
Inputs: args (required). Returns: result
app_exitA
Cleanly EXIT the app currently running on the Flipper over BLE (app_exit_request) — back to the desktop/menu. Use before app_launch if an app is already running. Real action — approve per call.
Inputs: no named parameters. Returns: result
app_get_errorARead-only
Read the running app's last error as a HUMAN-READABLE string over BLE (app_get_error). Call this when an app_launch / app_button / transmit returns a bare status code, to get the app's own error text. Read-only.
Inputs: no named parameters. Returns: result
app_launchA
Launch a Flipper app BY NAME over BLE (app_start_request) — skips UI navigation. name: exact app name, e.g. 'NFC', 'Sub-GHz', '125 kHz RFID', 'Infrared', 'GPIO', 'U2F', 'iButton', 'Bad USB' (get exact names from the USB read server's app_list). args (optional): a launch argument — typically a FILE PATH to open directly (a .sub/.nfc/.ir); many apps jump straight to that file. then_screenshot (default True): capture the first screen. FAILS if an app is already running (app_exit first) or the name is unknown. Real action.
Inputs: name (required), args, then_screenshot.
app_load_fileA
Open a specific saved file in its app over BLE (app_load_file_request) — e.g. load a .sub into Sub-GHz. ⚠️ The matching app must already be running (app_launch it first). Real action.
Inputs: path (required). Returns: result
app_lock_statusARead-only
Is an app currently running/locking the Flipper? over BLE (app_lock_status) — a good pre-check before app_launch. Read-only.
Inputs: no named parameters. Returns: result
desktop_is_lockedBRead-only
Is the Flipper's desktop PIN-locked? over BLE (desktop_is_locked). Read-only.
Inputs: no named parameters. Returns: result
desktop_unlockA
Clear the Flipper's desktop lock over BLE (desktop_unlock_request). Note: likely clears the swipe-lock only, not a numeric PIN. Real action.
Inputs: no named parameters. Returns: result
device_infoARead-only
Read the Flipper's device_info (60+ fields: firmware, hardware revision, radio stack, battery, etc.) WIRELESSLY over BLE, as a {field: value} map. Read-only.
Inputs: no named parameters.
find_my_flipperA
Make the Flipper beep + flash to locate it over BLE (system_play_audiovisual_alert) — the one 'output' reachable over BLE RPC (LED/vibro proper are CLI-only). Real action (noise + light).
Inputs: no named parameters. Returns: result
get_datetimeARead-only
Read the Flipper's real-time clock over BLE (system_get_datetime). Read-only.
Inputs: no named parameters. Returns: result
gpio_readARead-only
Read a GPIO pin over BLE (gpio_read_pin). pin: PC0|PC1|PC3|PB2|PB3|PA4|PA6|PA7. Read-only. (Corrects the earlier 'GPIO is CLI-only' note — GPIO IS in the RPC schema.)
Inputs: pin (required). Returns: result
gpio_set_modeA
Set a GPIO pin mode over BLE (gpio_set_pin_mode). pin: PC0|PC1|PC3|PB2|PB3|PA4|PA6|PA7; mode: output|input. Real action.
Inputs: pin (required), mode. Returns: result
gpio_writeA
Set a GPIO OUTPUT pin over BLE (gpio_write_pin). pin: PC0|PC1|PC3|PB2|PB3|PA4|PA6|PA7; value 0/1. Set the pin to OUTPUT first via gpio_set_mode. Real action.
Inputs: pin (required), value (required). Returns: result
healthwatchA
Manage the M5 unattended HEALTH-WATCH — a scheduled, READ-ONLY job that polls the Flipper (battery / storage / clock / firmware / reachability) and fires a macOS notification on anomalies (low/aging/hot battery, full SD, clock drift, firmware change). DEFAULT-OFF; this tool is the on/off switch. When enabled it runs 3×/day (09:00 / 15:00 / 21:00 local) via a launchd LaunchAgent. action: 'status' (default) — enabled? + the last snapshot summary (read-only, no device poll). 'on' — enable the 3×/day schedule (load the LaunchAgent). 'off' — disable it (back to default-off). 'run' — run ONE read-only health check right now and return the summary. The job is structurally incapable of transmit/write (hardcoded read-only command allowlist).
Inputs: action. Returns: result
pingARead-only
Ping the Flipper over BLE (system_ping) — liveness + round-trip echo check. Read-only.
Inputs: no named parameters. Returns: result
playbookARead-only
The operating manual for driving this Flipper efficiently over BLE. CALL THIS FIRST in a fresh session before navigating the device: returns the data-first control algorithm, verified menu maps (main menu, Momentum settings, region-bypass path), app-entry recipes, input/widget conventions, and key device behaviors. Read-only, no device action.
Inputs: no named parameters. Returns: result
power_infoARead-only
Detailed battery/power info over BLE (system_power_info) as a {field: value} map: voltage, current, charge %, temperature, charging state. Read-only.
Inputs: no named parameters.
pressA
Inject a UI button over BLE to drive the Flipper wirelessly. button: up|down|left|right|ok|back. kind: short|long|press|release (default short). then_screenshot (default True): capture the resulting screen in the SAME BLE connection so you SEE what changed. Real action — Claude Desktop prompts per call (the gate).
Inputs: button (required), kind, then_screenshot.
press_sequenceA
Inject a SEQUENCE of buttons in ONE BLE connection — efficient multi-step navigation (one connect instead of one per press). buttons: space-separated btn[:kind], e.g. 'down down ok' or 'right right ok:long'. then_screenshot (default True): capture the final screen in the same connection. Real actions — approve per call.
Inputs: buttons (required), then_screenshot.
read_latestARead-only
Read the MOST-RECENTLY-SAVED file in a Flipper folder over BLE (newest by timestamp) — e.g. pull the NFC card / Sub-GHz capture / RFID dump you just saved on the device. folder: e.g. '/ext/nfc', '/ext/subghz', '/ext/lfrfid', '/ext/infrared'. Returns decoded text or a binary summary. Read-only.
Inputs: folder. Returns: result
rebootADestructive
⚠️ Reboot the Flipper over BLE (system_reboot). mode: OS (normal, default) | DFU (bootloader) | UPDATE. Use OS as a recovery action when the device is wedged; the BLE link drops as it restarts. Real action — do NOT use DFU/UPDATE unless you mean it.
Inputs: mode. Returns: result
run_badusbADestructive
⚠️ Run a BadUSB (DuckyScript) payload over BLE: if content is given it's uploaded to path
(storage_write) first, then the Bad USB app is launched on that file and started (press OK).
path e.g. '/ext/badusb/demo.txt'. ⚠️ This injects keystrokes into whatever the Flipper is
USB-plugged into — YOUR OWN machine / authorized targets ONLY. Returns the run screen.
Real action — approve per call.
Inputs: path (required), content.
scanARead-only
Diagnostic: is the Flipper advertising over BLE right now? If not, it's most likely connected to your phone (only one BLE central at a time) or asleep. No device action.
Inputs: no named parameters. Returns: result
screenshotARead-only
📷 Capture the Flipper's 128x64 screen as a PNG over BLE — the agent's eyes, wireless. Read-only/observational (safe to auto-allow).
Inputs: no named parameters.
selftestARead-only
Daemon self-test / diagnostics: is the daemon up, is the BLE link connected, cached-device status, ping round-trip time, idle timer. Does NOT force a connect (reports current state). Read-only — call this to debug 'is the wireless toolkit healthy?'.
Inputs: no named parameters. Returns: result
set_datetimeA
Set the Flipper's clock over BLE (system_set_datetime). when='now' syncs to this Mac's time, or pass 'YYYY-MM-DD HH:MM:SS'. Real action.
Inputs: when. Returns: result
storage_deleteADestructive
⚠️ DELETE a file/dir on the Flipper over BLE (storage_delete_request). recursive=True for a non-empty dir. Real action — irreversible.
Inputs: path (required), recursive. Returns: result
storage_infoARead-only
Free/total space on a Flipper filesystem over BLE (storage_info_request). path: '/ext' (SD) or '/int' (internal). Read-only.
Inputs: path. Returns: result
storage_listARead-only
List a directory on the Flipper's SD/internal storage over BLE (storage_list_request). path: e.g. '/ext' (SD root), '/ext/subghz', '/ext/nfc', '/ext/infrared', '/int'. Dirs are tagged [DIR], files show their byte size. Read-only.
Inputs: path. Returns: result
storage_md5ARead-only
MD5 hash of a file on the Flipper over BLE (storage_md5sum_request) — integrity check. Read-only.
Inputs: path (required). Returns: result
storage_mkdirC
Create a directory on the Flipper over BLE (storage_mkdir_request). Real action.
Inputs: path (required). Returns: result
storage_readARead-only
Read a file from the Flipper's storage over BLE (storage_read_request). Returns decoded text
for text files (.sub / .nfc / .ir / configs, capped ~8 KB), or a binary summary + local path
otherwise. path: e.g. '/ext/subghz/Tesla/foo.sub'. ⚠️ BLE times out on LARGE files (firmware
#3174) — for big ones use the USB flipper server's storage_read. Read-only.
Inputs: path (required). Returns: result
storage_renameC
Rename/move a file or dir on the Flipper over BLE (storage_rename_request). Real action.
Inputs: old (required), new (required). Returns: result
storage_statARead-only
Stat a file/dir on the Flipper over BLE (storage_stat_request) — type (FILE/DIR) + size. Read-only.
Inputs: path (required). Returns: result
storage_writeA
⚠️ WRITE/UPLOAD a file to the Flipper over BLE (chunked storage_write_request). Provide EITHER content (text, written as UTF-8) OR local_path (a file on this Mac to upload). dest = full Flipper path, e.g. '/ext/subghz/foo.sub'. Overwrites. ⚠️ BLE is slow for large files — use USB for big ones. Real action.
Inputs: dest (required), content, local_path. Returns: result
transmit_infraredADestructive
⚠️ Open a saved Infrared remote over BLE — the app-driven IR path. Launches the Infrared app
with the .ir file as its launch arg, showing the remote's BUTTON LIST. path: e.g.
'/ext/infrared/TV.ir'. IR is one-command-per-button, so this opens the remote; then use press
(+ screenshot) to select a button and fire it. ⚠️ Real IR — your own devices. Approve per call.
Inputs: path (required), then_screenshot.
transmit_subghzADestructive
⚠️ TRANSMIT a saved Sub-GHz capture over BLE — the app-driven TX path (there is NO direct Sub-GHz TX RPC). Launches the Sub-GHz app with the file as its launch arg, which drives straight into the transmit flow. path: e.g. '/ext/subghz/Tesla/Tesla_US_AM650.sub'. The firmware's region check applies — a 'Transmission is blocked / missing region file' screen = the device's region lock (fix in Momentum settings, not here). ⚠️ Real RF — YOUR OWN TARGETS, LEGAL BANDS ONLY. Approve per call.
Inputs: path (required), then_screenshot.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Turns a phone into a camera+Bluetooth remote so AI assistants can see and control any PC.
Related MCP Servers
- 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.-
- 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 gradedqualityDmaintenanceControl a Govee BLE RGBIC LED strip from Claude (or any MCP client) over Bluetooth on macOS.MIT
- 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