ble-fleet-mcp
by JephinJose
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLEET_LOG_LEVEL | No | Log level; logs always go to stderr so stdout stays clean for the MCP stdio transport. | INFO |
| FLEET_TRACE_PATH | No | Where trace events are written. | .fleet_mcp/traces/trace.jsonl |
| FLEET_ALLOW_WRITES | No | Set to 1 to allow fleet_write. Off by default. | 0 |
| FLEET_BACKOFF_MAX_S | No | Cap on per-device retry backoff. | 30.0 |
| FLEET_TRACE_ENABLED | No | Structured JSONL tracing of pool/scheduler events. | 1 |
| FLEET_MAX_CONNECTIONS | No | Hard cap on simultaneous BLE connections. Match this to what you measured for your adapter — see docs/hardware-validation.md. | 4 |
| FLEET_DEVICE_TIMEOUT_S | No | Per-device timeout (connect + operation) before it's treated as a failure. | 10.0 |
| FLEET_BACKOFF_INITIAL_S | No | Initial per-device retry backoff. | 0.5 |
| FLEET_BACKOFF_MULTIPLIER | No | Exponential backoff multiplier. | 2.0 |
| FLEET_OPERATION_TIMEOUT_S | No | Default overall timeout for a fleet_read/fleet_write batch, after which unresolved devices report timeout and the rest of the batch is returned. | 60.0 |
| FLEET_CIRCUIT_BREAKER_THRESHOLD | No | Consecutive failures before a device is marked unhealthy and stops being retried. | 3 |
| FLEET_CIRCUIT_BREAKER_COOLDOWN_S | No | How long an unhealthy device is skipped before a single probe attempt is allowed through. | 60.0 |
| FLEET_REQUIRE_CONFIRMATION_SAFETY_CRITICAL | No | Whether safety_critical-tiered devices require explicit confirm_addresses on writes. | 1 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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/JephinJose/ble-fleet-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server