WPX AI MCP | Wireless Charging Device Connection & Protocol Analysis Guide

01

QUICK START

Connect in one simple step

Start with your device connected and the AI MCP panel showing that the service is running.

Copy the configuration, paste it into your AI Agent, and you are done.

Click “Copy configuration” at the bottom left of the panel. Paste it into an MCP-capable AI Agent platform that can access the service on your computer. AI handles setup and connects your device automatically.

Then ask AI: “What is the current device status?”

Closing the panel keeps the service running. AI MCP shares actions and data with the device GUI. “Stop MCP” does not disconnect the device or stop capture.

Ready to test? Just ask AI

Try: “Check the device status, start capture, and analyze the data.” AI will use the appropriate tools to carry out your request.

02

COPY. PASTE. CONNECT.

AI handles setup. You ask the questions.

Copy the full content from the WPX AI MCP panel and paste it into your AI Agent.

One copy and paste takes care of setup and connection.

The copied content includes the connection details for your AI Agent to handle automatically. Once connected, ask about device status, measurements, or Qi protocols in natural language.

Connected? Try these prompts

Manual configuration reference (optional)

Use the token from the status window

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.

General client

Streamable HTTP JSON

{
  "name": "WPX AI MCP",
  "transport": "streamable-http",
  "url": "http://127.0.0.1:8765/mcp",
  "headers": {
    "Authorization": "Bearer <real token from Copy configuration>"
  }
}

Codex

config.toml

[mcp_servers.wpx_ai]
url = "http://127.0.0.1:8765/mcp"
http_headers = { Authorization = "Bearer <TOKEN>" }

Successful connection The client should list tools starting with device_, wpx01a_, or wpxs1_.

POST /mcp

03

TOOL REFERENCE

Complete tool reference

The service exposes tools for the connected device type. Tools without listed parameters take no arguments.

Common devices

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.

WPX-01A

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=60` `max_points=120`	Read downsampled telemetry history for a selected time window.

WPX-S1

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=null` `limit=50` `modulation=null` `valid_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

Prompt examples

Ask the AI to check status first, then explicitly request telemetry or capture when needed.

General checkdevice_*

Check the connected device status, model, serial number, and firmware version, then list the available device-specific tools.

WPX-01A trendwpx01a_*

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.

WPX-S1 read-only checkwpxs1_*

Do not start capture. Read the WPX-S1 capture status, stream info, latest heartbeat, and pipeline statistics to assess the device link.

WPX-S1 packet analysiswpxs1_get_recent_packets

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

Security boundaries

MCP can operate real hardware. Treat the local endpoint, tokens, and device ownership as one security boundary.

Local only

The service listens only on 127.0.0.1. Do not proxy it, forward it, or change it to a LAN address.

Protect tokens

Do not publicly share configuration or screenshots containing tokens. After restarting the service, copy the current configuration from the panel again.

Single client

Connect only one AI client at a time so multiple agents cannot change capture or telemetry state concurrently.

Work with the device GUI

AI MCP shares actions and data with the current device GUI. Check the current state before starting or stopping capture.

Stop the service before leaving To finish testing, stop capture or telemetry first, then click “Stop MCP”. Closing the panel keeps the service running, and stopping MCP does not stop capture.

06

TROUBLESHOOTING

Troubleshooting

Check the status window, connection configuration, and device capture state in that order.

AI client cannot connect to the endpoint

Open the AI MCP panel and confirm that the service is running with a device connected. Copy the configuration again and paste it into your AI Agent platform. The platform must support MCP and reach http://127.0.0.1:8765/mcp on your computer using Streamable HTTP.

401 or token error

Return to the current AI MCP panel, click “Copy configuration” again, and paste the full content into your AI Agent platform so the agent can update the connection.

Port 8765 is already in use

Check for an existing WPX AI MCP service. To restart it, click “Stop MCP” in its panel before starting again. Closing the panel alone does not release the port.

Device-specific tools are missing

Call device_get_status and device_get_info first. Confirm the model and connection, then refresh the MCP tool list after fixing the issue.

WPX-01A has no telemetry data

Check the current telemetry state. If it has not started, call wpx01a_start_telemetry, wait for a sample, then read the latest value or history.

WPX-S1 has no packet or frequency data

Check capture status and stream info first. Call wpxs1_start_capture if capture has not started, or wpxs1_resume_capture when paused.

Does closing the panel or stopping MCP affect the device?

Closing the panel keeps the MCP service running. “Stop MCP” stops the AI connection service but does not disconnect the device or stop capture. End capture in the device GUI, or ask AI to stop it before stopping MCP.