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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dudebot/flipper-mcp-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server