Skip to main content
Glama
JephinJose

ble-fleet-mcp

by JephinJose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ble-fleet-mcp

No user-submitted related servers found.

    Related Servers

    • BLE MCP Server

      es617
      A
      license
      A
      quality
      C
      maintenance
      A stateful Bluetooth Low Energy (BLE) MCP server that enables AI agents to scan, connect, read/write characteristics, and subscribe to notifications on BLE devices.
      35
      18
      MIT

    • 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.
      21
      BSD 2-Clause "Simplified"
    • tinypilot-mcp by tiny-pilot

      tinypilot-mcpofficial

      tiny-pilot
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes fleet-aware KVM primitives for AI agents to control TinyPilot devices, including screen capture, keyboard input, mouse events, and device selection.
      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.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a distinct role: register, scan, read, write, watch, status, pool_status, and operation_status. The three 'status' tools are differentiated by scope (device health vs. pool telemetry vs. batch progress), though the naming overlap could cause minor confusion.

    Naming Consistency5/5

    All tools share the 'fleet_' prefix and use consistent snake_case. Actions are verbs (register, scan, read, write, watch), while queries are nouns (status, pool_status, operation_status), forming a predictable pattern.

    Tool Count5/5

    Eight tools is well-scoped for a fleet management server, covering core operations without unnecessary bloat. Each tool serves a clear purpose in the lifecycle.

    Completeness4/5

    The set covers discovery, registration, read/write, watching, device health, pool telemetry, and operation tracking. Missing a deregister or fleet deletion operation is a minor gap, but the primary workflows are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources