bluespy-mcp 1.3.1

MCP server for blueSPY Bluetooth LE protocol analyzer

blueSPY MCP Server

MCP server for the blueSPY Bluetooth LE protocol analyzer. Gives AI assistants direct access to .pcapng capture analysis — turn packet captures into conversations instead of writing scripts or scrolling through Wireshark.

Works with Claude Desktop, Claude Code, and Cursor.

What It Does

Instead of writing Python scripts or manually filtering packets, just ask:

"Load this capture and tell me what's going on."

The AI loads your capture file, classifies 54,000+ packets, identifies 219 devices, maps 25 connections, and gives you a structured breakdown — in seconds.

Example: Analyzing a Restaurant Bluetooth LE Environment

You: Load the First Watch capture and summarize it.

Claude: Loaded First Watch Carmel.pcapng — 54,195 packets over 32 seconds.

  219 devices detected, 25 active connections.

  Packet breakdown:
  → 11,671 ADV_IND (connectable advertisements)
  → 4,738 ADV_NONCONN_IND (beacons)
  → 6,554 LE_DATA (active data transfer)
  → 5,642 SCAN_REQ / 5,014 SCAN_RSP
  → 113 CRC errors from RF congestion
  → 33 new connections initiated

You: Show me the advertising for the first device.

Claude: Device BC:57:29:01:00:42 — 34 advertisements found.
  Channels: 37, 38, 39
  RSSI: min -82, max -48, avg -65.2

You: Find all the errors.

Claude: 113 errors found — all CRC failures on advertising channels,
  consistent with a congested RF environment (219 devices in range).

No scripts. No manual filtering. Just a conversation.

Prerequisites

• Python 3.10+
• blueSPY application (free) — provides the native libblueSPY library required for packet parsing

Download blueSPY for your platform from rfcreations.com/bluespy-software:

Platform	Download
macOS 11.0+	blueSPY-Darwin.pkg
Windows 7+	blueSPY-win64.msi
Windows 7+ (Portable)	blueSPY-win64.7z
Linux (glibc 2.27+)	blueSPY-Linux.7z
Linux (arm64)	blueSPY-Linux-arm64.7z
Linux (Headless)	blueSPY-Linux-Headless.7z

No hardware needed to get started — download the example captures from the same page and use them with the file analysis tools.

Installation

pip install bluespy-mcp

Or install from source:

git clone https://github.com/novelbits/bluespy-mcp.git
cd bluespy-mcp
pip install .

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "bluespy": {
      "command": "bluespy-mcp",
      "env": {
        "BLUESPY_LIBRARY_PATH": "/Applications/blueSPY.app/Contents/Frameworks/libblueSPY.dylib"
      }
    }
  }
}

Claude Code

claude mcp add bluespy -- bluespy-mcp

Or add to your .mcp.json:

{
  "bluespy": {
    "command": "bluespy-mcp",
    "env": {
      "BLUESPY_LIBRARY_PATH": "/Applications/blueSPY.app/Contents/Frameworks/libblueSPY.dylib"
    }
  }
}

Cursor

Add to your MCP server configuration:

{
  "bluespy": {
    "command": "bluespy-mcp",
    "env": {
      "BLUESPY_LIBRARY_PATH": "/Applications/blueSPY.app/Contents/Frameworks/libblueSPY.dylib"
    }
  }
}

Environment Variables

Variable	Description	Required
BLUESPY_LIBRARY_PATH	Path to libblueSPY.dylib / .so / .dll	Yes
BLUESPY_API_PATH	Path to directory containing bluespy.py (auto-discovered if not set)	No
BLE_CAPTURES_DIR	Default directory for capture files (default: captures/)	No

Platform-Specific Library Paths

Platform	Path
macOS	/Applications/blueSPY.app/Contents/Frameworks/libblueSPY.dylib
Windows	C:\Program Files\blueSPY\libblueSPY.dll
Linux	/usr/local/lib/libblueSPY.so

Tools

File Management

Tool	Description
load_capture(file_path)	Load a .pcapng capture file for analysis
close_capture()	Close the currently loaded file
list_captures(directory?)	List .pcapng files in a directory

Discovery

Tool	Description
capture_summary()	Packet counts by type, duration, device/connection counts
list_devices()	All Bluetooth devices with addresses and names
list_connections()	All connections with parameters

Analysis

Tool	Description
search_packets(summary_contains?, packet_type?, channel?, max_results?, start?)	Filter packets by criteria (paginated — returns has_more when truncated)
inspect_connection(connection_index)	Deep-dive connection analysis with packet breakdown
inspect_advertising(device_index)	Per-device advertising analysis with RSSI and channel stats
inspect_all_devices()	Batch advertising analysis for ALL devices in a single pass (much faster than per-device calls)
inspect_all_connections()	Batch connection analysis for ALL connections in a single pass (much faster than per-connection calls)
find_capture_errors(max_results?)	Error, failure, disconnect, and timeout packets

Live Hardware

Tool	Description
connect_hardware(serial, force)	Connect to first available device (or specify serial)
disconnect_hardware()	Disconnect from hardware
start_capture(filename, duration_seconds, LE, CL, QHS, wifi, CS)	Start live capture
stop_capture()	Stop active capture
hardware_status()	Get current hardware state

Resources

Resource	Description
capture://status	Current loaded file metadata (JSON)
bluespy://hardware	Current hardware connection state (JSON)
bluespy://capture	Current live capture state (JSON)

Prompts

Prompt	Description
analyze-capture	Guided workflow to load and analyze a capture file
quick-capture	Quick-start workflow for live hardware capture
debug-connection	Troubleshoot hardware connection issues

Try It Without Hardware

Download the example captures from RFcreations (free) and try these prompts. No sniffer needed — just the blueSPY application installed.

Example Captures

File	Packets	Devices	Connections	What's inside
LE_Phone_Alert_Status_Profile.pcapng	2,359	16	2	Simple Bluetooth LE GATT profile with scanning and data exchange
Encrypted Advertising Data.pcapng	1,547	13	0	Advertising only — no connections, good for device discovery analysis
AVDTP_and_eSCO.pcapng	—	—	—	Bluetooth Classic audio (A2DP streaming + voice calls)
BIS.pcapng	—	—	—	LE Audio Broadcast Isochronous Stream
CIS_and_AVDTP_and_HCI.pcapng	—	—	—	Mixed: LE Audio CIS + Classic audio + HCI commands
audiopod_LE_Audio_CIG.pcapng	53,887	186	14	Dense LE Audio capture — NRF5340 devices, CRC errors, encrypted traffic

Start here: simple Bluetooth LE profile

Load LE_Phone_Alert_Status_Profile.pcapng and tell me what's going on.

Inspect all connections. What protocols are being used?

Advertising-only analysis

Load Encrypted Advertising Data.pcapng. How many devices are advertising? Inspect all of them.

Search for SCAN_REQ packets. Which devices are being actively scanned?

Stress test: large LE Audio capture

Load audiopod_LE_Audio_CIG.pcapng and summarize it.

Inspect all 14 connections at once. Which ones have the most data packets?

Find all errors. What's causing the CRC failures?

Look at connection 9 — that's the NRF5340_AUDIO device. What's it doing?

Or use the built-in analyze-capture prompt for a guided walkthrough of any file.

Live Hardware Capture

Important: Close the blueSPY desktop application before using live hardware capture. Only one application can control the sniffer at a time. If the device LED is green, it's already in use — close blueSPY (or any other client) until the LED turns blue.

If you have a blueSPY sniffer connected via USB, the MCP server can control it directly — connect, start/stop captures, and analyze results in real time.

You: Connect to my sniffer and capture Bluetooth LE traffic for 10 seconds.

Claude: Connected to Moreph serial 2411001234.
  Capturing Bluetooth LE packets for 10 seconds...
  Capture complete — saved to ble_capture_20260228.pcapng (12,847 packets).

You: Summarize what you captured.

Claude: 12,847 packets over 10 seconds.
  87 devices detected, 12 active connections.
  → 4,231 ADV_IND (connectable advertisements)
  → 1,892 ADV_NONCONN_IND (beacons)
  → 3,104 LE_DATA (active data transfer)

Hardware access is subprocess-isolated — if a hardware call hangs, the MCP server kills the worker process and stays responsive. A file lock (~/.bluespy-mcp.lock) ensures only one client controls the hardware at a time.

Model Recommendations

This MCP server works with any LLM that supports tool use. The built-in prompt templates (analyze-capture, quick-capture, debug-connection) guide even smaller models through the correct multi-step workflows.

Tier	Models	Best For
Minimum	Haiku 4.5, GPT-4o mini, Gemini Flash	Loading captures, running guided workflows, basic summaries. Handles the full tool chain reliably.
Recommended	Sonnet 4.5, GPT-4o, Gemini Pro	Deeper protocol analysis — correlating error patterns across connections, interpreting RSSI trends, diagnosing RF interference, generating actionable recommendations.
Advanced	Opus, o3, Gemini Ultra	Multi-capture comparison, cross-referencing against Bluetooth spec, complex protocol-level debugging. Rarely needed.

Key factors for good results:

• Use the prompt templates. They walk any model through load → summarize → analyze → inspect in the right order.
• Tool-use reliability matters more than model size. A mid-tier model that follows tool sequences correctly will outperform a large model that skips steps.
• Domain knowledge helps but isn't required. The server returns structured JSON with classified packet types, so the model doesn't need to know Bluetooth LE internals to report useful findings.
• Extended thinking is unnecessary. The tasks here are tool-calling and summarization, not complex reasoning. Standard inference is faster, cheaper, and equally effective. Keep extended thinking disabled.

Development

git clone https://github.com/novelbits/bluespy-mcp.git
cd bluespy-mcp
pip install -e .
pytest

To run the full test suite including end-to-end and hardware tests (requires a blueSPY sniffer connected via USB):

pip install -e ".[e2e]"
bash scripts/test.sh all

Troubleshooting

"blueSPY library not found"

Ensure BLUESPY_LIBRARY_PATH points to the correct native library for your platform. The blueSPY application must be installed from rfcreations.com.

"No capture file loaded"

Use load_capture() with a path to your .pcapng file before calling analysis tools.

Claude Desktop crashes on startup

If you're using FastMCP v3.0.2+, ensure the server runs with show_banner=False (this is the default in bluespy-mcp). The FastMCP banner corrupts the MCP stdio protocol.

Hardware: "bluespy_init failed"

The MCP server retries automatically when this happens, but if it persists:

1. Connect directly to your computer — do not use a USB hub. The Moreph sniffer requires a direct USB connection for reliable communication.
2. Close the blueSPY desktop app if it's open. Only one application can control the hardware at a time. Check the device LED: green means it's in use, blue means it's available.
3. Unplug and replug the device, then try again.

Hardware: "in use by another session"

This means the file lock (~/.bluespy-mcp.lock) is held by another MCP session. If no other session is actually running (e.g., a previous session crashed), use the force parameter:

connect_hardware(force=True)

This removes the stale lock file and proceeds with the connection.

Hardware: Python crash on exit

Fixed in v1.3.0. If you're on an older version, upgrade with pip install --upgrade bluespy-mcp.

Module not found errors

Ensure you're using Python 3.10+ and have installed the package:

python --version  # Should be 3.10+
pip install bluespy-mcp

License

MIT License. See LICENSE for details.

Links

• blueSPY by RFcreations
• MCP Protocol
• Issues