Skip to main content
Glama
sbrunner-atx

io.github.sbrunner-atx/wsjtx-mcp

by sbrunner-atx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.sbrunner-atx/wsjtx-mcp

No user-submitted related servers found.

    Related Servers

    • shack-mcp

      alphamonkey
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an LLM operate an amateur radio shack: query live APRS traffic, predict satellite passes, schedule SDR captures, and monitor FT8/WSPR band activity.
      MIT

    • MultiViewer

      RobSpectre
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for agents to control MultiViewer, the best way to watch motorsports. Works locally or remotely.
      19
      MIT

    • hamqth-mcp

      qso-graph
      A
      license
      A
      quality
      D
      maintenance
      MCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.
      8
      25 PyPI
      GPL 3.0

    • qrz-mcp

      qso-graph
      A
      license
      A
      quality
      F
      maintenance
      MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.
      6
      3
      GPL 3.0

    • OBS MCP Server

      royshil
      A
      license
      B
      quality
      F
      maintenance
      A server that provides tools to control OBS Studio remotely via the OBS WebSocket protocol, enabling management of scenes, sources, streaming, and recording through an MCP client interface.
      100
      139 npm
      132
      GPL 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map to distinct WSJT-X actions, and the descriptions are detailed enough to avoid confusion in normal use. The main risks are the generic wsjtx_call escape hatch, which overlaps with several specific tools, and the 'transmit' tool, whose name suggests starting transmission but actually halts it.

    Naming Consistency3/5

    Tool names are readable and consistently snake_case, but there is no uniform verb_noun pattern: some are nouns (status, decodes, log), some are single verbs (reply, clear, configure), and some are phrases (switch_config, free_text). The 'transmit' name is also semantically inverted from the action it performs.

    Tool Count5/5

    Fourteen tools is within the well-scoped range for a WSJT-X control server. Each tool covers a distinct functional area, and the generic wsjtx_call fills protocol-level gaps without making the set feel bloated.

    Completeness4/5

    The set covers the core WSJT-X UDP workflow: reading status, decodes, and logged QSOs; replying to calls; sending free text; halting TX; configuring; clearing; highlighting; switching configurations; and annotating calls. Minor gaps exist around dial-frequency control and enumerating configurations, but the wsjtx_call escape hatch and external rig control provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources