radiochron-mcp

radiochron.com · the chronicle of your radio.

A local-first Model Context Protocol server for Wi-Fi incident diagnosis and Bluetooth Low Energy observation. It combines native radio collection with the radiochron Rust core, then returns typed conclusions instead of forcing an assistant to interpret raw operating-system output.

The preferred MCP revision is 2025-11-25; clients that request 2025-06-18 receive the compatible legacy tool shape. Every tool has input and output schemas, structured content, safety annotations, explicit execution semantics, cancellation where work is long-running, and actionable separation between JSON-RPC protocol errors and tool execution errors.

RadioChron repositories remain independent:

• radiochron is the Rust/IoT core.

• radiochron-js is the Node/npm library; it does not ship MCP.

• radiochron-mcp is this pure-Rust MCP server.

• radiochron-agent is the unattended durable collector/exporter and does not depend on MCP.

• radiochron-electron is the standalone desktop app and does not depend on MCP.

Install

The npm package carries verified native binaries for Windows x64, Linux x64/ARM64, Intel Mac, and Apple Silicon:

claude mcp add radiochron -- npx -y radiochron-mcp

Or install the Rust binary from source:

cargo install --git https://github.com/sergii-ziborov/radiochron-mcp

Building on Debian/Ubuntu requires libdbus-1-dev and pkg-config for the BlueZ adapter. Prebuilt npm users do not need a Rust toolchain.

Register an installed binary with any stdio MCP client:

{
  "mcpServers": {
    "radiochron": {
      "command": "radiochron"
    }
  }
}

RADIOCHRON_CHRONICLE_PATH optionally overrides the local chronicle path: %LOCALAPPDATA%\RadioChron on Windows, ~/Library/Application Support/RadioChron on macOS, or the XDG state directory on Linux.

Start with one tool

Use diagnose_incident first. One request returns independent sections for:

• current Wi-Fi interfaces and association;

• RF/environment analysis;

• radio → authentication → DHCP → gateway → DNS → TCP → Internet stages;

• Windows WLAN event history when available;

• recent change-only chronicle entries;

• an optional native BLE advertisement scan, normalized identities, retained histories, and evidence-based findings.

One unavailable collector does not discard the rest of the incident. Each section has ok, data, or an actionable error, and the top-level problems list is compact enough for an assistant to explain directly. Targets are never contacted unless the caller supplies them.

Tool surface

Seventeen tools are portable. Windows exposes an eighteenth, wifi_history, backed by WLAN AutoConfig.

ble_scan uses WinRT on Windows, BlueZ on Linux, and CoreBluetooth on macOS. It listens only for devices observed during the requested scan window, does not perform GATT connections, and feeds the same privacy-minimized RadioChron tracker used by explicit ble_observe calls. iBeacon and Eddystone UID data can provide stronger protocol identity; generic private addresses remain ephemeral.

On macOS 11+, the host application or terminal launching the MCP process must have Bluetooth permission. An app bundle needs NSBluetoothAlwaysUsageDescription; a terminal-launched server requires Bluetooth access for that terminal in System Settings. Linux requires a running BlueZ service and access to the system D-Bus.

MCP behavior

• Newline-delimited UTF-8 JSON-RPC 2.0 over stdio; stdout contains MCP frames only.

• Negotiates both 2025-11-25 and 2025-06-18, preferring the current revision.

• Current tool definitions declare execution.taskSupport: "forbidden" because this local stdio server uses normal cancelable requests rather than durable experimental tasks.

• Unknown methods and malformed call envelopes use JSON-RPC errors.

• Tool input/radio/platform failures use isError: true so a model can correct arguments or explain the platform problem.

• Structured results are also serialized into text content for older clients.

• Source files are architecture-gated at 300 lines; real stdio conformance tests cover current and legacy lifecycle/catalog/error behavior.

The protocol layer is deliberately implemented without an MCP SDK so its lifecycle and error behavior remain small and auditable. Native BLE collection does use btleplug and tokio; these host dependencies stay in this MCP repository and do not enter the portable/no-std radiochron core.

Safety and privacy

SSIDs, BSSIDs, Bluetooth addresses, advertisement payloads, and event logs can be sensitive. The server has no telemetry and sends nothing off the machine. The chronicle writes only its rotating local JSONL file. Saved Wi-Fi passwords are never read.

RSSI is signal evidence, not physical distance or direction. Private Bluetooth addresses can rotate, so clone/recurrence claims require protocol identity or caller-provided identity. Native BLE scanning never connects to peripherals.

The MCP surface intentionally excludes plaintext Wi-Fi keys, adapter MAC changes, adapter restarts, computer rename, active LAN sweeps, arbitrary shell execution, and external AI review.

Release

Releases are assembled from one green cross-platform CI run. The npm archive must contain revision-matched binaries and provenance sidecars for all five targets. After public npm verification, publish the matching server.json to the official MCP Registry and only then create/push the matching immutable tag.

License

Licensed under the MIT License. The underlying radiochron Rust core remains separately dual-licensed under MIT or Apache-2.0.