LOCAL DEVICE BRIDGE
Switch a selected WPX device to AI MCP mode in the device manager. The local service owns the device connection so an MCP-capable AI client can safely call measurement and analysis tools.
01
QUICK START
Device connection and AI client connection are separate steps. Follow this order.
Open the WPX device manager, wait for the scan to finish, and select a device in normal mode.
Select “AI MCP” mode and start it. A regular device window and MCP mode cannot use the same device at the same time.
Configure the client after the status changes to “Service ready”. Keep the status window open.
Click “Copy configuration” in the status window, paste it into the AI client, and complete the MCP connection.
http://127.0.0.1:8765/mcp
WPX-S1 MCP mode only establishes the device and service connection.
Capture starts only after wpxs1_start_capture; WPX-01A telemetry must also be started explicitly.
02
CLIENT CONFIGURATION
Every client connects to the same local Streamable HTTP endpoint.
The snippets below are format templates and cannot connect on their own. After each startup, copy the configuration with the current token from the status window.
{
"name": "WPX AI MCP",
"transport": "streamable-http",
"url": "http://127.0.0.1:8765/mcp",
"headers": {
"Authorization": "Bearer <real token from Copy configuration>"
}
}[mcp_servers.wpx_ai]
url = "http://127.0.0.1:8765/mcp"
http_headers = { Authorization = "Bearer <TOKEN>" }device_, wpx01a_, or wpxs1_.
03
TOOL REFERENCE
The service exposes tools for the connected device type. Tools without listed parameters take no arguments.
Available for every MCP-capable device.
| Tool | Parameters | Purpose |
|---|---|---|
device_get_status | None | Read service, device connection, and current runtime status. |
device_get_info | None | Read device identity, version, and capability information. |
Identity refresh and explicit telemetry control.
| Tool | Parameters | Purpose |
|---|---|---|
wpx01a_refresh_identity | None | Refresh serial number, firmware, and hardware identity. |
wpx01a_start_telemetry | None | Start receiving live WPX-01A telemetry. |
wpx01a_stop_telemetry | None | Stop telemetry while keeping the data already buffered. |
wpx01a_get_latest_telemetry | None | Read the latest available telemetry sample. |
wpx01a_get_telemetry_history |
seconds=60max_points=120 |
Read downsampled telemetry history for a selected time window. |
Capture lifecycle, protocol packets, frequency, and pipeline diagnostics.
| Tool | Parameters | Purpose |
|---|---|---|
wpxs1_start_capture | None | Start a new capture session from the stopped state. |
wpxs1_pause_capture | None | Pause delivery of the current capture to clients. |
wpxs1_resume_capture |
reset_time_base=true |
Resume a paused capture; reset the display time base by default. |
wpxs1_stop_capture | None | Stop the current capture and freeze its completed state. |
wpxs1_get_capture_status | None | Read capture state, session, and counter summaries. |
wpxs1_get_stream_info | None | Read the device-declared sample rate and stream parameters. |
wpxs1_get_recent_packets |
cursor=nulllimit=50modulation=nullvalid_only=false
|
Page through recent protocol packets, filtering by modulation and validity. |
wpxs1_get_latest_frequency | None | Read the latest carrier-frequency state. |
wpxs1_get_latest_heartbeat | None | Read the latest device heartbeat and error counters. |
wpxs1_get_pipeline_statistics | None | Read cumulative USB, queue, and parsing-pipeline statistics. |
04
PROMPT EXAMPLES
Ask the AI to check status first, then explicitly request telemetry or capture when needed.
Check the connected device status, model, serial number, and firmware version, then list the available device-specific tools.
Start WPX-01A telemetry, wait for stable samples, read up to 120 points from the last 60 seconds, and summarize power, voltage, current, and temperature changes.
Do not start capture. Read the WPX-S1 capture status, stream info, latest heartbeat, and pipeline statistics to assess the device link.
Start WPX-S1 capture, read the latest 50 valid protocol packets, group them by ASK/FSK, and summarize repeated headers, checksum anomalies, and timing order.
05
SECURITY BOUNDARIES
MCP can operate real hardware. Treat the local endpoint, tokens, and device ownership as one security boundary.
The service listens only on 127.0.0.1. Do not proxy it, forward it, or change it to a LAN address.
Do not share configuration, screenshots, or tokens. Old tokens should not be reused after the service stops.
Connect only one AI client at a time so multiple agents cannot change capture or telemetry state concurrently.
Do not open a regular device window or another serial tool while MCP mode is active.
06
TROUBLESHOOTING
Check the status window, connection configuration, and device capture state in that order.
Make sure the status window is open and shows “Service ready”. The address must be http://127.0.0.1:8765/mcp and the transport must be Streamable HTTP.
Do not reuse an old token manually. Return to the current status window, click “Copy configuration”, and replace the client URL and Authorization header.
Close another WPX AI MCP status window or the old process using that port, then restart the service. Do not bind the service to an external network address.
Call device_get_status and device_get_info first. Confirm the model and connection, then refresh the MCP tool list after fixing the issue.
Telemetry is off by default. Call wpx01a_start_telemetry, wait for a sample, then read the latest value or history.
Capture is off by default. Call wpxs1_start_capture, check capture status and stream info, and use wpxs1_resume_capture when paused.
This is expected. The status window owns the local service and device connection. Re-enter AI MCP mode and copy a new configuration before reconnecting.