Skip to main content
Glama
jt-mcp

jt-mcp

by qso-graph

jt-mcp

PyPI

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 install

Related 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

jt_cq

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

jt_status

What each WSJT-X is doing: dial frequency and band, mode, DX call and grid, Tx enabled or transmitting, your call and grid

jt_decodes

Recent decodes, each read into its parts (who is calling whom, grid, report, sign-off); filter by callsign, CQ only, SNR, band

jt_heard

Stations heard: how often, last SNR, last grid, mode and band

jt_wspr

WSPR spots WSJT-X decoded: call, grid, power, SNR, drift

jt_diagnostics

The listener: where it listens, who may send, what arrived, what was dropped and from where, each WSJT-X's version

get_version_info

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-mcp

ChatGPT 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

--bind ADDR

127.0.0.1

where to listen for WSJT-X

--allow ADDR

this PC

a PC that may send; repeatable; required with a network --bind

--udp-port N

2237

WSJT-X's UDP Server port

--transport

stdio

streamable-http binds 127.0.0.1 only

--port N

8031

the streamable-http port

License

GPL-3.0-or-later. See LICENSE.

Available Tools

7 tools
get_version_infoGet Version InfoA
Read-onlyIdempotent

Get this server's version, what it does, and where its work is tracked.

Inputs: no named parameters. Returns: object

jt_cqJt CqA
Read-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 DecodesB
Read-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 DiagnosticsB
Read-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 HeardB
Read-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 StatusA
Read-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 WsprA
Read-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

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessMixed handling

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables querying WSPR beacon data including live spots, band activity, top beacons, propagation paths, and SNR trends through any MCP-compatible AI assistant.
      9
      74 PyPI
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      14
      44 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for querying Kismet Wireless systems, enabling AI agents to retrieve network status, datasources, devices, and alerts via REST API.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      1
      MIT