A
licenseA
qualityC
maintenanceA 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
69 PyPI
19
MIT
ble-fleet-mcp
by JephinJose
Related Servers
Alternatives to ble-fleet-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets multiple AI coding agents coordinate as a swarm, with agent registration, task queues, messaging, a shared knowledge base, and fleet-wide machine capacity tracking.MIT
- AlicenseNot gradedqualityFmaintenanceBluetooth Low Energy (BLE) MCP server that allows AI agents to scan, connect to and communicated with BLE devices, as well as simulate BLE perhipherals.25BSD 2-Clause "Simplified"
- AlicenseNot gradedqualityCmaintenanceEnables centralized MCP server management with connection pooling, a live activity dashboard, and macOS menu bar integration for AI coding agents.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server enabling real-time communication, task delegation, and acknowledgment among multiple AI agents through a single local endpoint.71 npm5MIT
- AlicenseAqualityCmaintenanceMCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.2114 npm1MIT
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
ActivityStale
ResponsivenessNo issues