Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Bluetooth LE Health Sensors

by K-Dense-AIversion 0.1.3i★ 32 (Stars for the whole repo)iRuns on your computerRepository ↗
Registry nameio.github.K-Dense-AI/labmcp-ble-health

How to install

What it does

MCP server for Bluetooth LE health sensors (standard GATT profiles).

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Clinics & health

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Bluetooth LE Health Sensors. Follow https://mcp.popnx.com/i/k-dense-ai-labmcp-ble-health.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Bluetooth LE Health Sensors for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "labmcp-ble-health": { "command": "uvx", "args": [ "labmcp-ble-health" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Bluetooth LE Health Sensors tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "labmcp-ble-health": {
          "command": "uvx",
          "args": [
            "labmcp-ble-health"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Bluetooth LE Health Sensors and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Bluetooth LE Health Sensors or shows a Bluetooth LE Health Sensors tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Bluetooth LE Health Sensors yet

Bluetooth LE Health Sensors runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Bluetooth LE Health Sensors

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Clinics & health that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Bluetooth LE Health Sensors for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user labmcp-ble-health -- uvx labmcp-ble-health 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Bluetooth LE Health Sensors tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user labmcp-ble-health -- uvx labmcp-ble-health
  4. Type /mcp in Claude Code

    You should see Bluetooth LE Health Sensors listed as connected

  5. Try it

    Use Bluetooth LE Health Sensors and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Bluetooth LE Health Sensors or shows a Bluetooth LE Health Sensors tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Bluetooth LE Health Sensors for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "labmcp-ble-health": { "command": "uvx", "args": [ "labmcp-ble-health" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Bluetooth LE Health Sensors tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Bluetooth LE Health Sensors and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Bluetooth LE Health Sensors or shows a Bluetooth LE Health Sensors tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Bluetooth LE Health Sensors for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "labmcp-ble-health": { "type": "stdio", "command": "uvx", "args": [ "labmcp-ble-health" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Bluetooth LE Health Sensors tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Bluetooth LE Health Sensors and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Bluetooth LE Health Sensors or shows a Bluetooth LE Health Sensors tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Bluetooth LE Health Sensors💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user labmcp-ble-health -- uvx labmcp-ble-health

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "labmcp-ble-health": {
      "command": "uvx",
      "args": [
        "labmcp-ble-health"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "labmcp-ble-health": {
      "command": "uvx",
      "args": [
        "labmcp-ble-health"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "labmcp-ble-health": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "labmcp-ble-health"
      ]
    }
  }
}

Values you fill in

  • LABMCP_ADDRESS env
    Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE env
    Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY env
    Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS env
    Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
32 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings
Downloads per weeki
41/wk
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.1.3
Published to registryi
Sep 27, 2026
Code last changedi
Sep 27, 2026
Maker
K-Dense-AI
Packages
pypi: labmcp-ble-health
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account K-Dense-AI, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for labmcp-ble-health@0.1.3

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/k-dense-ai-labmcp-ble-health.svg)](https://mcp.popnx.com/en/servers/k-dense-ai-labmcp-ble-health)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Clinics & healthi

  • More stars than 0% of the other 1190 servers in this category
  • Published to the registry more recently than 36% of the other 1190 servers in this category
  • Basic checks equal to or better than 99% of the other 1190 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bluetooth LE Health Sensors safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.3) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

by medplumWidely used★ 2.8KUpdated 4 months ago

Runs in the cloud✓ service owner · medplum.com

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

by thetahealthGrowing↓ 725/wk★ 1.6KUpdated yesterday

Runs on your computer✓ thetahealth.ai

Codescene MCP Server

An MCP server that provides CodeScene Code Health analysis tools.

by codescene-ossGrowing↓ 3.8K/wk★ 85Updated 8 months ago

Runs on your computer✓ service owner · codescene.com

Marrow

Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.

by skeletonarmytechEarly↓ 62/wk★ 5Updated 29 days ago

Runs on your computer✓ skeletonarmy.tech
Compared with similar ones
This one
Bluetooth LE Health Sensors
Medplum MCPMirobodyCodescene MCP ServerMarrowWHOOP — MissingMCP
Runs whereInstalls on your computerRuns in the cloud, nothing to installInstalls on your computerInstalls on your computerInstalls on your computerRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/43/32/33/32/4
LicenseApache-2.0Apache-2.0Apache-2.0NOASSERTIONMITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Bluetooth LE Health Sensors — MCP Server

Let an AI agent read any Bluetooth Low Energy sensor that implements the standard Bluetooth SIG health profiles: record heart rate with RR intervals and HRV from a chest strap, read SpO2 and pulse rate from an oximeter, and capture blood pressure, body temperature and weight readings from monitors, thermometers and scales, in physiology labs, sports-science studies, sleep/HRV research and lab-operations settings.

[!WARNING]

Research and lab-operations use only. This is not a medical device. It is not intended for diagnosis, monitoring of patients, triage, or any clinical decision-making, and has not been validated or cleared by any regulator. Consumer sensors can be inaccurate; values pass through an AI agent that can misread them. Never use this server's output to make health decisions. Readings of people are personal data: follow your ethics approval and data-protection rules.

Packagelabmcp-ble-health
InstrumentsAny device implementing the Bluetooth SIG profiles: heart-rate straps/armbands (Heart Rate Service 0x180D), pulse oximeters (Pulse Oximeter Service 0x1822), blood pressure monitors (0x1810), thermometers (Health Thermometer 0x1809), weight scales (Weight Scale 0x181D), plus Battery (0x180F) and Device Information (0x180A)
InterfacesBluetooth Low Energy, via bleak (Linux/BlueZ, macOS/CoreBluetooth, Windows/WinRT)
ProtocolBluetooth SIG GATT: GATT Specification Supplement, HRS 1.0, PLXS 1.0.1, BLS 1.1.1, HTS 1.0, WSS 1.0.1; IEEE 11073-20601 SFLOAT/FLOAT per the PHD Transcoding White Paper v16
Status🧪 simulated: tested against a simulated BLE backend that emits byte-exact GATT packets, not yet verified on hardware. Report a hardware test

Try it without hardware

uvx labmcp-ble-health --simulate --check

The simulator provides six devices (addresses 00:00:5E:00:53:01–06, from the IANA documentation range): a combined "health kit" (default) exposing every service, and a separate HR strap, oximeter, BP monitor, thermometer and scale. Pick one with e.g. --simulate --address 00:00:5E:00:53:04.

Connect your device

  1. Check the device uses the standard profiles. Only devices that implement the Bluetooth SIG services above work. Many consumer wearables (most smartwatches, many fitness bands, several BP-monitor and scale brands) use proprietary protocols instead, and some only speak the standard profile in a "pairing"/"data transfer" mode. Chest straps that advertise the Heart Rate Service are the most reliable choice for HRV work.
  2. Free the device. A BLE sensor usually accepts one connection: close the vendor's phone app (or switch phone Bluetooth off) before connecting.
  3. Find the address: start the server without --address and ask the agent to run scan_devices, or run it with --check after putting the device in advertising mode (wear the strap; press the monitor's Bluetooth/start button). On Linux/Windows the address is the MAC (AA:BB:CC:DD:EE:FF); on macOS it is a CoreBluetooth UUID that is specific to your computer.
  4. Test the connection:
   uvx labmcp-ble-health --address AA:BB:CC:DD:EE:FF --check                       # Linux / Windows

uvx labmcp-ble-health --address 1A2B3C4D-1111-2222-3333-444455556666 --check # macOS

   Devices that require bonding (common for BP monitors and scales): add `--option pair=true` on Linux/Windows; macOS shows a system pairing prompt automatically. On Linux choose a non-default adapter with `--option adapter=hci1`; lengthen device discovery with `--option connect_timeout_s=40` (at most 60 s).

macOS: the terminal (or MCP client app) that launches the server needs Bluetooth permission (System Settings › Privacy & Security › Bluetooth). Without it macOS terminates the process as soon as Bluetooth is touched (exit code 134), before any error message can be printed.

Add to your MCP client

Claude Code

claude mcp add hr-strap -- uvx labmcp-ble-health --address AA:BB:CC:DD:EE:FF

Claude Desktop / Cursor / Windsurf (claude_desktop_config.json, .cursor/mcp.json, …)

{

"mcpServers": { "hr-strap": { "command": "uvx", "args": ["labmcp-ble-health", "--address", "AA:BB:CC:DD:EE:FF"] } } }

Every tool is read-only (nothing on the device is changed, no control points are written), so --read-only makes no difference. Run one server entry per device if you use several sensors at once. For other clients, generate the snippet with uvx labmcp config ble-health --address AA:BB:CC:DD:EE:FF --client vscode (also cursor, codex, claude-code).

Tools

ToolKindDescription
get_command_log👁 readReturn the most recent raw commands sent to / replies received from the instrument (newest last). Useful for debugging and for recording what was done.
get_connection_info👁 readReport which instrument is connected (identity, address, simulated or real), whether the server is read-only, and the active safety limits. Call this first.
get_device_info👁 readRead the device's identity (manufacturer, model, serial, firmware), the standard health services it exposes and its features.
read_battery👁 readRead the device's battery level (Battery Service, 0-100 %).
read_pulse_oximetry👁 readRead SpO2 (%) and pulse rate from a pulse oximeter, averaged over a few seconds or as a single spot-check reading.
read_temperature👁 readWait for a thermometer to send a temperature measurement and return it in °C.
read_weight👁 readWait for a scale to send a weight measurement (kg), with BMI and height if the scale sends them.
reconnect🛑 safetyClose and re-open the connection to the instrument (e.g. after it was power cycled or a cable was re-plugged).
record_heart_rate👁 readRecord heart rate for duration_s: bpm series, RR intervals and time-domain HRV (mean HR, SDNN, RMSSD, pNN50).
scan_devices👁 readScan for nearby Bluetooth LE devices: address, name, signal strength and advertised health services. Works without a configured --address.
wait_for_blood_pressure👁 readWait for a blood pressure monitor to send a measurement: systolic, diastolic and mean arterial pressure (mmHg) and pulse rate.

get_connection_info, get_command_log and reconnect are built into every LabMCP server.

Safety limits

LimitDefaultMeaning
max_record_duration_s600 sLongest heart-rate recording or continuous-oximetry averaging window an agent may start
max_wait_s300 sLongest time a tool may wait for a blood pressure, temperature, weight or spot-check reading

Override at launch: --limit max_record_duration_s=1800. Note that many MCP clients also enforce their own per-tool-call timeout; long recordings may need that raised too (e.g. MCP_TOOL_TIMEOUT in Claude Code).

Example prompts

  • "Record 5 minutes of heart rate from the chest strap and give me mean HR, SDNN and RMSSD, and save the raw RR intervals to ~/hrv/p07_baseline.csv."
  • "Scan for heart-rate straps nearby and tell me which one has the strongest signal."
  • "Wait for the blood pressure monitor: I'll start the cuff now. Report systolic/diastolic and whether the device flagged movement or an irregular pulse."
  • "Average SpO2 and pulse rate over 30 seconds from the oximeter and tell me how many samples were unusable."
  • "Read the scale when the participant steps on it and log weight and BMI with the device timestamp."
  • "What's the battery level of the strap before we start the session?"

Notes

  • Measurement devices push, they are not polled. Blood pressure monitors, thermometers, scales and spot-check oximeters only *indicate* a value when a measurement completes (these characteristics cannot be read). Call the tool first, then take the measurement. The tool keeps scanning and reconnecting until its timeout because many monitors only advertise right after measuring (for oximeters this needs mode="spot_check"; auto must connect first to find out which mode the device supports).
  • One measurement at a time. Starting a measurement cancels one that is still running on the same server (for example a recording whose tool call already timed out in the MCP client), and reconnect cancels it too; the cancelled call returns an error.
  • Malformed packets are skipped and logged (get_command_log) rather than discarding the whole recording; record_heart_rate and read_pulse_oximetry report how many in malformed_packets.
  • `save_path` (record_heart_rate) must be a new .csv file: ~ is expanded, missing folders are created, and an existing file is never overwritten. It is checked before recording starts.
  • Stored measurements. Monitors send unsent stored readings back-to-back, oldest first, when they connect. Tools keep listening 1.5 s after the first one and return the newest as the result, listing older ones in other_measurements; the device clock time is in device_timestamp (device local time, often wrong if the clock was never set).
  • Special values (IEEE 11073 NaN, NRes, ±INF) are never turned into numbers: they are reported as null with an explanation (special_values, unavailable_samples). Oximeters typically send NaN for the first seconds while acquiring.
  • Units: blood pressure in kPa is converted to mmHg (1 kPa = 7.500617 mmHg), °F to °C, lb to kg; unit_reported says what the device sent. Weight resolution is 0.005 kg / 0.01 lb per the Weight Scale spec; 0xFFFF means "measurement unsuccessful" and is returned as weight_kg: null. Energy expended is in kJ (HRS 1.0).
  • HRV is computed from the RR intervals the sensor sends (unit 1/1024 s): SDNN (sample SD), RMSSD, pNN50. RR intervals outside 0.3–2.0 s are excluded as artefacts; no further artefact correction or ectopic-beat editing is done. If a notification is lost over the air, the successive difference across that gap is not a true beat-to-beat difference. Optical wrist sensors often send no RR intervals at all. Use a validated ECG system for anything beyond exploratory research.
  • The Enhanced Blood Pressure Measurement, Record Access Control Point (downloading a monitor's whole memory), Current Time and User Data services are not implemented; nothing is ever written to the device.
  • Bluetooth pairing, bonding keys and OS permissions are handled by the operating system; the server never sees PINs.

Hardware verification

ModelFirmwareInterfaceVerified byDate
*none yet: be the first*