jt-mcp
Read-only monitoring of WSJT-X UDP traffic for CQ calls, decodes, heard stations, WSPR spots, radio status, and listener diagnostics.
jt_cq: find who is calling CQ and classify the CQ type, e.g. plain, DX, POTA/SOTA activity, contest, region, or frequency; filter by band, instance, modifier, and time window.jt_status: show each WSJT-X instance’s dial frequency, band, mode, DX call/grid, Tx state, and your call/grid.jt_decodes: list recent decoded messages with parsed CQ/caller/grid/report/sign-off details; filter by callsign, CQ-only, SNR, band, instance, limit, and time window.jt_heard: summarize stations heard since startup: count, last SNR, last grid, mode, band, first/last heard; sort and filter by callsign/time.jt_wspr: list WSPR spots decoded by WSJT-X, including call, grid, power, SNR, and drift; filter by callsign, band, limit, and time window.jt_diagnostics: inspect the UDP listener, allowed senders, received/dropped datagrams, drop sources, and each WSJT-X instance’s version/heartbeat.get_version_info: get server version, purpose, and work-tracking information.
It never sends WSJT-X messages, keys a transmitter, or changes settings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jt-mcp Who's calling CQ POTA on 20 meters right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jt-mcp
Ask an AI app what WSJT-X is hearing. WSJT-X sends what it is doing and every decode to a UDP Server address; jt-mcp listens there and answers: who is calling CQ, and what kind of CQ (DX, POTA, a contest, a region), who has been heard and how well, what WSJT-X is tuned to, recent decodes and WSPR spots.
Read-only, permanently. jt-mcp never sends WSJT-X a message, so it cannot answer a call, key your transmitter or change a setting. No write, no PTT, no transmit control—a permanent constraint, not a first-version limit. The tests assert it against the source.
WSJT-X first, and WSJT-X defines the protocol. The UDP message definitions come from the
WSJT-X project—Network/NetworkMessage.hpp, at the schema WSJT-X states—because the project
that owns a definition is its authority. The code is
qso-graph-lib's. Part of the
qso-graph project.
Install
uvx jt-mcp # run it; nothing to installRelated MCP server: io.github.sbrunner-atx/wsjtx-mcp
Set up WSJT-X
In WSJT-X: File, Settings, Reporting, UDP Server: 127.0.0.1, port 2237 (WSJT-X's
defaults). That is all jt-mcp needs when WSJT-X runs on the same PC.
Only one program can listen on a UDP port. If GridTracker, JTAlert or another logger already
listens on 2237, give jt-mcp a different port (--udp-port) and point WSJT-X at that one.
Tools
Tool | Answers |
| Who is calling CQ, and what kind: plain, DX, activity (POTA, SOTA, WWFF, IOTA), contest (TEST, FD, RU, WW), region (NA, EU, ...), or a frequency (CQ 290). The latest per station |
| What each WSJT-X is doing: dial frequency and band, mode, DX call and grid, Tx enabled or transmitting, your call and grid |
| Recent decodes, each read into its parts (who is calling whom, grid, report, sign-off); filter by callsign, CQ only, SNR, band |
| Stations heard: how often, last SNR, last grid, mode and band |
| WSPR spots WSJT-X decoded: call, grid, power, SNR, drift |
| The listener: where it listens, who may send, what arrived, what was dropped and from where, each WSJT-X's version |
| Service version and status |
Times are UTC. Several WSJT-X instances (two radios, two bands) are kept apart by the Id each
sends, such as WSJT-X - FT-991A.
Questions it will answer
"Who's calling CQ POTA on 20 m right now?"
"Any DX calling CQ in the last ten minutes, strongest first?"
"Has W9XYZ been heard, and how strong?"
"What is WSJT-X tuned to, and is Tx enabled?"
"Why isn't anything showing up?"—
jt_diagnostics
Configure your MCP client
jt-mcp works with any MCP-compatible client. Add the server and restart the client.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS,
%APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"jt": {
"command": "uvx",
"args": ["jt-mcp"]
}
}
}Claude Code
claude mcp add jt -- uvx jt-mcpChatGPT Desktop
Configure via Settings > Apps & Connectors, or in your agent definition, with the same
command and args as above.
WSJT-X on another PC
By default jt-mcp listens on 127.0.0.1, this PC alone. For WSJT-X on another PC, give one
address of this PC with --bind, and name each PC that may send with --allow:
"args": ["jt-mcp", "--bind", "192.168.1.50", "--allow", "192.168.1.40"]and set WSJT-X's UDP Server to 192.168.1.50. Listening on every interface at once
(0.0.0.0) is refused, --allow is required with a network address, and names are not
accepted, only IP addresses. A datagram from anyone else is dropped unread and counted, and
jt_diagnostics shows the count and the addresses.
What the allow list does not do. It keeps other machines out. It is not proof of who sent: a UDP sender's address can be forged by anything on the same network. What contains that is that jt-mcp only reads, so a forged datagram can mislead about what WSJT-X is doing and cannot make anything happen.
Options
jt-mcp [--bind ADDR] [--allow ADDR ...] [--udp-port N]
[--transport stdio|streamable-http] [--port N] [--version] [--help]Option | Default | |
|
| where to listen for WSJT-X |
| this PC | a PC that may send; repeatable; required with a network |
|
| WSJT-X's UDP Server port |
|
|
|
|
| the streamable-http port |
License
GPL-3.0-or-later. See LICENSE.
Available Tools
7 toolsget_version_infoGet Version InfoARead-onlyIdempotent
Get this server's version, what it does, and where its work is tracked.
Inputs: no named parameters. Returns: object
jt_cqJt CqARead-onlyIdempotent
Who is calling CQ, and what kind of CQ: plain, DX, an activity (POTA, SOTA, WWFF, IOTA), a contest (TEST, FD, RU, WW), a region (NA, EU, ...), or a frequency (CQ 290). The latest CQ per station, newest first.
Inputs: band, cq_type, instance, modifier, +1 more. Returns: object
jt_decodesJt DecodesBRead-onlyIdempotent
Recent decodes, newest first, each read into its parts: CQ (with its type), or who is calling whom, with the grid, report or sign-off it carries.
Inputs: band, limit, cq_only, min_snr, +3 more. Returns: object
jt_diagnosticsJt DiagnosticsBRead-onlyIdempotent
The listener itself: where it listens, who may send, what has arrived, what was dropped and from where, and each WSJT-X instance's version and last heartbeat.
Inputs: no named parameters. Returns: object
jt_heardJt HeardBRead-onlyIdempotent
Stations heard since this server started: how often, last SNR, last grid sent, mode and band, first and last heard.
Inputs: sort, limit, callsign, since_minutes. Returns: object
jt_statusJt StatusARead-onlyIdempotent
What each running WSJT-X is doing now: dial frequency and band, mode, the station being worked (DX call and grid), whether Tx is enabled or transmitting, and your own call and grid.
Inputs: instance. Returns: object
jt_wsprJt WsprARead-onlyIdempotent
WSPR spots WSJT-X has decoded, newest first: call, grid, power, SNR, drift.
Inputs: band, limit, callsign, since_minutes. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: version info, listener diagnostics, live WSJT-X status, CQ filtering, raw decodes, aggregated heard stations, and WSPR spots. The only mild overlap is between jt_decodes, jt_cq, and jt_heard, since CQs and heard stations are derived from decodes, but the descriptions clarify their different filters and aggregations.
Six of seven tools share a consistent `jt_` prefix with resource-oriented names (jt_status, jt_cq, jt_decodes, etc.), and the lone `get_version_info` is a minor deviation. The set is readable and predictable, though it does not follow a strict verb_noun pattern.
Seven tools is a well-scoped size for a read-only WSJT-X monitoring server. Each tool covers a distinct slice of the domain and none feels redundant or missing.
The surface covers version info, listener health, live status, CQ monitoring, decoded traffic, heard-station aggregation, and WSPR spots, which is strong for an observational server. It does not offer any control or QSO logging operations, but those may be intentionally out of scope for this monitoring-focused MCP.
Maintenance
Related MCP Connectors
Read-only access to your MetaTrader 4 and 5 accounts for AI agents: balances, open positions, trade history with win rate, live quotes, symbol specs and candles. It cannot place, modify or close orders.
Live amateur-radio APRS data: stations, tracks, weather, telemetry, packets and nets (read-only).
Read-only Linux server and Docker monitoring for AI assistants: CPU, memory, disk, network.
Ask your AI about construction and ad-platform data. Read-only on your systems, never writes to them
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables querying WSPR beacon data including live spots, band activity, top beacons, propagation paths, and SNR trends through any MCP-compatible AI assistant.974 PyPIGPL 3.0
- AlicenseAqualityBmaintenanceAn MCP server that controls WSJT-X for amateur radio weak-signal modes (FT8/FT4, etc.) via UDP, enabling observation of status and decodes, and transmit operations like replying to CQs or sending free text.1444 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for querying Kismet Wireless systems, enabling AI agents to retrieve network status, datasources, devices, and alerts via REST API.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to observe and inspect Sierra Chart chartbooks, charts, studies, drawings, and data, read diagnostics, and apply validated configuration changes via a local bridge, without any order execution or trading features.1MIT