flipper-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLIPPER_PORT | No | Explicit serial port for the Flipper Zero device (e.g., /dev/ttyACM1). If not set, auto-detection is used based on USB manufacturer or VID:PID, falling back to /dev/ttyACM0. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| device_infoA | Return the Flipper's device_info dict (firmware, hardware, radio, etc.). |
| list_ir_filesA | List .ir files under a directory on the Flipper's SD card (non-recursive). |
| list_ir_buttonsB | Parse a saved .ir file on the Flipper and return its buttons. |
| send_ir_buttonB | Transmit a named button from a saved .ir file on the Flipper. Raises on CLI error. |
| send_ir_signalA | Transmit an ad-hoc parsed IR signal. |
| delete_ir_buttonB | Remove a named button from an .ir file (reads, filters, rewrites). |
| list_universal_remotesA | List the built-in universal IR remote names on this firmware (ac, tv, fans, ...). |
| list_universal_signalsB | List the signal names available for a built-in universal remote (e.g. POWER, VOL+). |
| send_universal_signalB | Transmit a named signal from a built-in universal remote (e.g. remote='ac', signal='OFF'). |
| learn_ir_buttonA | Put Flipper in IR RX, wait for a single remote press (up to timeout_seconds), then append the captured signal as a named button to the given .ir file. Creates the file if it doesn't exist. The user must press a physical remote at the Flipper during the capture window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct action or resource: device_info for hardware info, list_* for browsing, learn_* for capturing, send_* for transmitting, and delete_* for removal. No two tools overlap in purpose.
Most tools follow a verb_ir_noun or verb_universal_noun pattern (e.g., delete_ir_button, send_universal_signal). The one exception is device_info, which uses noun_noun, breaking the pattern slightly.
With 10 tools, the server covers the core IR workflows (browse, learn, send, delete) without being overwhelming. The count feels well-scoped for the domain.
Basic IR operations are covered, but there are gaps: no tool to delete an entire .ir file, rename a file or button, or directly create an empty file. These missing operations may cause workflow dead ends.