Skip to main content
Glama
es617

BLE MCP Server

by es617
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to BLE MCP Server

No user-submitted related servers found.

    Related Servers

    • blew BLE MCP

      stass
      A
      license
      Not graded
      quality
      D
      maintenance
      Bluetooth Low Energy (BLE) MCP server that allows AI agents to scan, connect to and communicated with BLE devices, as well as simulate BLE perhipherals.
      18
      BSD 2-Clause "Simplified"

    • lw-ble-mcp

      zevonlin
      A
      license
      B
      quality
      B
      maintenance
      A lightweight Bluetooth Low Energy debug MCP server for AI agents. It provides 21 tools for BLE scanning, connection, GATT read/write, descriptor access, MTU query, notification subscription, device recon, and engine diagnostics.
      21
      Apache 2.0

    • ble-fleet-mcp

      JephinJose
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing large fleets of BLE devices with connection pooling, scheduling, retries, and partial-failure handling. Enables AI agents to run fleet-level reads/writes without worrying about radio connection limits.
      8
      1
      MIT

    • btdiag

      Crsuraj1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control Bluetooth audio devices via MCP tools, including battery status, connect/disconnect, find-my, and snoop decoding.
      MIT

    • mimoe-agent

      dcaicedo
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the mimOE AI Agent, enabling on-device tools like device discovery, network insight, and persistent note storage via natural language.
      -
    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 35 tools

    Disambiguation5/5

    Each tool targets a distinct BLE operation, from scanning to connection management, GATT operations, subscriptions, spec/plugin management, and tracing. Even similar notification tools are clearly differentiated by behavior (blocking, non-blocking, batch).

    Naming Consistency5/5

    All tools follow a consistent snake_case convention prefixed with 'ble_', using a noun_verb pattern (e.g., ble_scan_start, ble_connect, ble_read). The grouping by domain (scan, connection, spec, plugin) is logical and predictable.

    Tool Count4/5

    35 tools cover a complex domain comprehensively, but the count is slightly high. However, each tool serves a specific purpose, so the scope is justified without unnecessary overlap.

    Completeness5/5

    The surface covers the full BLE lifecycle: scanning, connection, GATT discovery, read/write, notifications, descriptors, plus advanced features like spec management, plugins, tracing, and task management. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources