Skip to main content
Glama
pogorelov-labs

flipper-ble-mcp

by pogorelov-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to flipper-ble-mcp

No user-submitted related servers found.

    Related Servers

    • FlipperTalk

      ReconGrunt
      A
      license
      A
      quality
      B
      maintenance
      Talk 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.
      66
      MIT

    • govee-mcp

      RishaanJ
      A
      license
      Not graded
      quality
      D
      maintenance
      Control a Govee BLE RGBIC LED strip from Claude (or any MCP client) over Bluetooth on macOS.
      MIT

    • Flipper Zero MCP Server

      busse
      A
      license
      Not graded
      quality
      D
      maintenance
      Modular 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.
      31
      MIT

    • panda-mcp

      lkathke
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns a comma.ai Panda into a conversational CAN reverse-engineering rig, allowing users to record, diff, find signals, and send frames through natural language with Claude.
      2
      MIT

    • Serial MCP Server

      Hejun1998
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools like Claude Code and Codex CLI to read and write serial port data, facilitating embedded development workflows such as coding, flashing, and debugging.
      23 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 38 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources