efferent-ble-simulator
Allows AI agents to control and monitor simulated Bluetooth Low Energy (BLE) peripheral devices — FTMS smart trainers, cycling power meters, speed/cadence sensors, and heart rate monitors — over real radio via MCP tools.
Enables simulated BLE devices (FTMS, power, speed/cadence, heart rate) to be discovered and used by Garmin cycling apps, providing a virtual trainer for training and performance analysis.
Enables simulated BLE devices (FTMS, power, speed/cadence, heart rate) to be discovered and used by Strava cycling apps, providing a virtual trainer for training and performance analysis.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@efferent-ble-simulatorStart an FTMS smart trainer simulation with target power 200W"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Efferent simulates Bluetooth Low Energy (BLE) peripheral devices over a real radio (Linux BlueZ): FTMS smart trainers, cycling power meters, speed/cadence sensors and heart rate monitors. It exposes an MCP server (stdio or HTTP) so AI agents — and the bundled Web dashboard — can start, configure and monitor simulations as if controlling a real trainer.
Features
4 device types over real BLE radio: FTMS smart trainer (0x1826), Cycling Power (0x1818), Speed/Cadence (0x1816), Heart Rate (0x180D)
Full FTMS control point support: Request Control / Start / Stop / Reset / Set Target Power / Set Resistance / Set Indoor Bike Simulation Params
Dynamic simulation: human-like power/cadence drift + physics-based speed model (weight, grade, Crr, CdA), 5 riding scenarios including the scripted ride_script
Hot parameter update: change params while running — the connected phone keeps its link and receives new values on the next notify (no re-pair)
Named config presets: save / load / rename / delete up to 20 named configs, shared between MCP and Dashboard
17 MCP tools for agents: control, configure, config presets, interaction rules, sessions, logs, live device state, version
Web dashboard (React + shadcn/ui): status, forms, one-click ride templates, interaction rules, session/config management, live log side-panel
Docker Compose one-command deployment (MCP + Dashboard + Skill file over HTTP), long-running with health checks
Versioned: MCP
serverInfo.version+ble_get_versionlet agents detect updates
Related MCP server: pyBTMCP
Runtime Environment
Requirement | Detail |
OS | Linux only — the simulator drives the host BlueZ over D-Bus |
BlueZ | ≥ 5.87 (5.86 has an advertisement-registration bug) |
Hardware | A BLE-capable adapter (built-in or USB dongle) is required to actually broadcast |
D-Bus policy |
|
Docker | The mcp container mounts the host D-Bus socket; the BLE radio always stays on the host |
Not supported | macOS / Windows natively (would need a different BLE stack); without any BLE adapter the MCP service runs but nothing is transmitted |
Architecture
┌──────────────┐ MCP protocol ┌───────────────────────────┐
│ AI Agent / │ ◄───────────────► │ MCP Server (HTTP :3300) │
│ MCP Client │ stdio / :3300 │ Web Dashboard (:3330) │
│ (Claude, │ └────────────┬──────────────┘
│ Codex, pi) │ │ BlueZ D-Bus (system bus)
└──────────────┘ ▼
┌───────────────────────────┐
│ Host Linux BlueZ │
│ bluetoothd + BLE adapter │
│ (D-Bus policy, ≥ 5.87) │
└────────────┬──────────────┘
│ HCI / radio
▼
┌───────────────────────────┐
│ BLE advertisement + GATT │
│ FTMS / Power / CSC / HR │
└────────────┬──────────────┘
│
┌────────────▼──────────────┐
│ Phone / Cycling App │
│ (Zwift, Garmin, Strava...)│
└───────────────────────────┘Device Types
Type | BLE Service | Characteristics |
FTMS smart trainer | 0x1826 | FM Feature, Indoor Bike Data (notify), Control Point (write/indicate), Status, Resistance/Power ranges |
Cycling Power | 0x1818 | Power/Cadence measurement, wheel & crank data |
Speed/Cadence (CSC) | 0x1816 | Wheel & crank revolution counters |
Heart Rate | 0x180D | HR measurement, body sensor location, battery |
Quick Start
Prerequisites
Linux with BlueZ ≥ 5.87 (bluetoothd) and a BLE-capable adapter
BlueZ 5.86 has an advertisement-registration bug; on kernels with strict MGMT validation every
RegisterAdvertisementfails. Upgrade first:sudo pacman -S bluez && sudo systemctl restart bluetooth(Arch) /sudo apt install bluez(Debian).Node.js ≥ 18
1. Native install
npm install
npm run setup # sudo — installs D-Bus policy, enables bluetoothd, verifies GATT
npm run build
npm run start:http # HTTP mode on :3300 (or npm start for stdio)npm run setup writes /etc/dbus-1/system.d/ble-simulator.conf — required for non-root GATT registration (without it the device advertises but cannot be connected).
2. Docker Compose (recommended for servers)
bash scripts/docker-up.sh # host prep (sudo, once) + build + startURL | Purpose |
| MCP endpoint |
| Web dashboard |
| Operation skill (for agents) |
| Dashboard help page |
Zero-compile build (better-sqlite3 prebuilt binary); on restricted networks use a mirror:
NPM_REGISTRY=https://registry.npmmirror.com \
BETTER_SQLITE3_BINARY_HOST_MIRROR=https://registry.npmmirror.com/-/binary/better-sqlite3 \
bash scripts/docker-up.shManagement: bash scripts/docker-up.sh status|logs|down
MCP Tools (17)
Tool | Purpose |
| Start / stop / restart a simulation |
| Controller state + active config + live device state (phase/power/cadence/HR) |
| Update config — hot-updates in place if running with the same device type |
| Current/latest config as JSON (form backfill) |
| Save current params as a named preset (max 20) |
| List / view saved presets |
| Rename / delete a preset |
| Custom BLE write-response rules |
| Session history / detail |
| Persistent communication logs (connect/write/notify/error) |
| MCP + Skill versions, changelog, Skill URL (for update detection) |
Example
{
"method": "tools/call",
"params": {
"name": "ble_start",
"arguments": {
"deviceType": "ftms",
"ftms": { "simulation": { "enabled": true, "scenario": { "type": "ride_script" } } }
}
}
}Dynamic Simulation
Enable via simulation on FTMS / CyclingPower / CSC:
"simulation": {
"enabled": true,
"riderWeightKg": 75, "bikeWeightKg": 8, "crr": 0.004, "cdA": 0.35,
"fatigueFactor": 0.0005, "cadenceCoupling": "proportional", "microPauseProbability": 0.008,
"autoStart": true,
"scenario": { "type": "ride_script" }
}Param | Default | Description |
|
| Master switch |
| 75 / 8 | Speed physics (rider+bike mass) |
| 0.004 / 0.35 | Rolling resistance / drag area |
| 0 | Power decay per minute (0 = none) |
|
|
|
| 0.005 | Per-tick coasting pauses |
|
| Start riding without an app sending Start |
|
| Riding scenario (below) |
Scenarios
steady— natural micro-variation onlyfreeride(default) — base power drifts ±20% every 60–180sintervals— high/low power alternationwarmup_main_cooldown— warmup → main → cooldownride_script— scripted ride: a sequence of riding actions (start / cruise / climb / sprint / coast / stop), each with target power, grade and optional cadence; auto-starts, loops withrepeat: true,stopzeroes power/cadence/speed. Omitphasesto use the built-in default script.
Hot Update & Stable Serial
Hot update:
ble_configurewhile running + same device type applies params in place — the connected phone keeps its link and receives updated values on the next notify. Device-type changes still restart (new serial forces re-discovery).Stable serial:
SIM_SERIAL_STABLE=1keeps the serial stable across same-type sessions (SIM001-FTMS), so a phone can reconnect after stop/start without forgetting the device.
Environment Variables
Var | Default | Description |
|
|
|
|
| HTTP listen address |
|
| Advertised name prefix |
| — | Instance ID mode for the device name |
| unset |
|
|
| Public Skill URL (returned by |
Source Layout
src/
├── index.ts # entry, lifecycle
├── mcp-server.ts # 17 MCP tool definitions & handlers
├── ble-controller.ts # BlueZ D-Bus lifecycle, advertisement, hot-update
├── database.ts # SQLite layer (sessions / saved_configs / logs)
├── config.ts # config merge & defaults
├── version.ts # version single-source
├── simulator.ts # HeartRate / Battery simulators
├── cycling-simulator.ts # power/cadence simulators + physics + ride_script engine
└── devices/ # heart-rate / cycling-power / csc / ftms GATT devicesBLE peripheral access runs over the host BlueZ D-Bus (the container mounts the host D-Bus socket). See docs/design/*.md for design records.
License
MIT © BLE Simulator Contributors
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceBluetooth Low Energy (BLE) MCP server that allows AI agents to scan, connect to and communicated with BLE devices, as well as simulate BLE perhipherals.15BSD 2-Clause "Simplified"
- FlicenseNot gradedqualityNot gradedmaintenanceA BLE fitness device simulator that enables AI agents to control simulated heart rate monitors, treadmills, and cycling trainers via the Model Context Protocol. It integrates ESP32 firmware, an MQTT broker, and a FastAPI backend for comprehensive device management and real-time interaction.
- AlicenseAqualityCmaintenanceA stateful Bluetooth Low Energy (BLE) MCP server that enables AI agents to scan, connect, read/write characteristics, and subscribe to notifications on BLE devices.3517MIT
- FlicenseNot gradedqualityBmaintenanceExposes Garmin Connect data and workout management to AI agents, supporting tools, resources, and prompts for health data, workout creation, and coaching workflows.1
Related MCP Connectors
Multi-tenant Telegram gateway for AI agents — HTTP+stdio, 8 tools, MTProto User API
Run, build, and validate firmware on virtual hardware from your AI agent. Hardware knowledge corpus.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
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/dncore/efferent-ble-simulator'
If you have feedback or need assistance with the MCP directory API, please join our Discord server