jt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The streamable-http port (--port N); default 8031 | 8031 |
| UDP_PORT | No | WSJT-X's UDP Server port (--udp-port N); default 2237 | 2237 |
| BIND_ADDR | No | Where to listen for WSJT-X (--bind ADDR); default 127.0.0.1 | 127.0.0.1 |
| TRANSPORT | No | Transport to use: stdio or streamable-http (--transport); streamable-http binds 127.0.0.1 only; default stdio | stdio |
| ALLOW_ADDR | No | A PC that may send datagrams (--allow ADDR); repeatable; required with a network --bind |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get this server's version, what it does, and where its work is tracked. |
| jt_statusA | 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. |
| jt_cqA | 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. |
| jt_decodesB | 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. |
| jt_heardB | Stations heard since this server started: how often, last SNR, last grid sent, mode and band, first and last heard. |
| jt_wsprA | WSPR spots WSJT-X has decoded, newest first: call, grid, power, SNR, drift. |
| jt_diagnosticsB | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.