Skip to main content
Glama

fldigi-mcp

Project page: ae5vg.com/products/fldigi-mcp

An MCP server for controlling fldigi, the popular amateur-radio digital-modem application, from MCP-aware clients such as Claude Desktop.

fldigi ships a built-in XML-RPC control interface. fldigi-mcp connects to it and exposes the whole API as a small set of logically-grouped MCP tools, so an assistant can read the radio's state and drive the modem, rig, log, and transmitter through plain language.

Status: beta. Signal hunting (find, name and tune to a station from the receiver audio, 0.2.0) and full API coverage (every one of fldigi's 174 XML-RPC methods is reachable through a named operation, enforced by a test), callsign-gated transmit, and an optional experimental Band Guidance feature. Supports the current fldigi release, 4.2.13, verified live on 2026-09-09.

📻 A field-tested fldigi XML-RPC API reference (free community resource)

Building this server meant mapping fldigi's entire XML-RPC interface and verifying every method against a live build — so we've written it all up and are sharing it freely, whether or not you ever use this MCP server:

  • docs/fldigi-api.md — a clean, complete, human-readable reference organized by namespace, with transport details, types, worked examples, a transmit-safety section, and field-tested gotchas.

  • docs/fldigi-api.pdf — the same, as a printable PDF.

  • docs/fldigi-api-spec.md — a terse, machine-readable catalog of all 174 methods (args, return type, read/write/keying).

Verified live against fldigi 4.2.13 via fldigi.list on 2026-09-09 (the method list is identical to 4.2.11, first verified 2026-06-23). It's more complete and current than the public wiki (it documents methods the wiki omits, e.g. TxID, and flags deprecated ones). Independent project — not affiliated with the fldigi / W1HKJ project. Corrections welcome via issues / PRs.

Related MCP server: contest-mcp

Highlights

  • Complete control — every one of the 174 XML-RPC methods in fldigi 4.2.13 is reachable through a named operation in one of the grouped tools (one permission each; all 22 tools are listed under Tools); tests/test_coverage.py fails the build if a method of the shipped catalog is not wired or an argument type disagrees with fldigi's signature. The fldigi_call escape hatch remains for methods a newer build may add.

  • Safe by default — the callsign is the single transmit gate. With no callsign configured the station is receive-only; nothing can key the radio.

  • Names match fldigi — tools and operations mirror fldigi's own API namespaces and on-screen labels (Op Mode, AFC, SQL, Rev, Lock, RxID/TxID, T/R).

  • No fragile dependencies — talks to fldigi with Python's standard-library xmlrpc.client. The only third-party runtime deps are the MCP SDK and PyYAML (for the optional band-plan data).

Why XML-RPC (and not a third-party library)

fldigi's XML-RPC interface is its official, OS-independent control API. This project talks to it directly rather than through an unmaintained wrapper, keeping the moving parts to Python's standard library and fldigi's own API.

Requirements

To install the desktop connector (.mcpb) all you need is:

  • fldigi running (its XML-RPC server is on by default at 127.0.0.1:7362).

Claude Desktop's uv runtime supplies Python and the dependencies, so end users do not install Python or uv themselves. (That runtime is currently marked experimental, so a recent Claude Desktop is recommended.)

For development from source you additionally need Python 3.10+ and uv (and Node.js, only for the MCP Inspector).

Install

Easiest: the desktop connector

Download fldigi-mcp.mcpb from the latest release, then in Claude Desktop open Settings → Desktop app, click Manage next to Extensions, and drag the file onto that page (or use Advanced settings → Install extension). It then shows as a connector under Settings → Customize → Connectors. A short settings form asks for your callsign (everything else has a default). No terminal, no Python, no uv to install.

👉 New to this? Follow the simple step-by-step install guide. Also see the install & safety model.

Add the operating skills

The desktop connector installs only the server. Its operating skills are separate downloads: fldigi-operating.skill and signal-hunting.skill, from the latest release or ae5vg.com/downloads.html. In Claude, open Customize → Skills, click Add, then Upload skill, and choose all the files at once.

For Claude Code or another MCP client, copy the folders under skills/ into the client's skills folder, for Claude Code ~/.claude/skills/.

To run the server itself in Claude Code, Codex, Cursor or VS Code, see Other AI assistants for the command or configuration block to copy.

From source (development)

git clone https://github.com/sbrunner-atx/fldigi-mcp.git
cd fldigi-mcp
uv sync

Then add it to Claude Desktop's config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "fldigi": {
      "command": "uv",
      "args": ["--directory", "/absolute/path/to/fldigi-mcp", "run", "fldigi-mcp"],
      "env": { "FLDIGI_CALLSIGN": "AE5VG" }
    }
  }
}

Restart Claude Desktop and ask "What's fldigi's status?". Omit the env block to run receive-only.

Try it with the MCP Inspector

uv run mcp dev src/fldigi_mcp/server.py

The Signal Browser patch (patches/) — proposed, not yet merged

Status: offered to fldigi's maintainer on 11 September 2026 (w1hkj/fldigi issue 55). Until it is merged, the method names and fields below are a proposal and may change.

fldigi's Signal Browser, the left-hand panel that decodes up to 30 PSK, RTTY or CW stations at once, is not on its XML-RPC API. patches/fldigi-4.2.13-browser-xmlrpc.patch touches four files (psk_browser.h/.cxx, viewpsk.cxx, xmlrpc.cxx) and adds two methods, browser.get_channels (array of {channel, freq, active, text}, text untrimmed, line breaks kept, accumulated since the last clear) and browser.clear. The browser tool and signal_hunt method="browser" use them and say so when fldigi is unpatched. A second patch, patches/fldigi-4.2.13-rsid-hits.patch (applies on top of the first), adds rsid.get_hits and rsid.clear: the RSID bursts the detector accepted, as {utc, mode, hz}. With RSID set to notify-only, fldigi then names the modes on the band without ever switching the modem; the rsid tool reads the list. Both patches are proposed, not merged. Tested on 4.2.13 (macOS, four synthetic PSK31 stations from 0 to -26 dB: all four copied in full). The patch applies to the fldigi git HEAD on SourceForge and is prepared for upstream submission; until it lands, build fldigi from source with it:

tar xf fldigi-4.2.13.tar.gz && cd fldigi-4.2.13
patch -p1 < /path/to/fldigi-mcp/patches/fldigi-4.2.13-browser-xmlrpc.patch
./configure --prefix=$HOME/.local/fldigi && make -j8 && make install

Tools

Each tool is one permission and takes an operation argument, so e.g. "change the mode" is a single permission regardless of which underlying method runs.

Tool

Controls (fldigi area)

status

quick snapshot: version, mode, frequency, T/R, callsign, band

diagnostics

host/network info for connectivity troubleshooting (no fldigi connection)

application

program info + launch/stop the fldigi process (fldigi.*)

modem

Op Mode / modem select, carrier, bandwidth, AFC range, Olivia

frequency

dial frequency and waterfall sideband

controls

AFC, SQL, Rev, Lock, RxID, TxID, status fields

transmit

T/R, Tune, abort, disable/enable Tx, macros, send — callsign-gated

rig

CAT control: mode, frequency, bandwidth, notch, QSY, meters

log

Logbook / contest fields; ADIF last/all records

text

RX/TX text and data streams

spot

spotting / PSK Reporter

wefax

WEFAX (weather fax) mode

navtex

NAVTEX / SitorB mode

flmsg

flmsg (message forms) interworking

io

ARQ / KISS I/O port selection

legacy

deprecated methods fldigi still serves, each with its current equivalent named

band_guidance

advisory band/watering-hole help (experimental)

signal_hunt

find and name the signals in the receiver audio; rank CQing stations (experimental, [hunt] extra)

tune_to

set modem and carrier to a signal_hunt candidate, receive only

browser

fldigi's Signal Browser: every station the decoder bank holds, with its text (needs the fldigi patch in patches/)

rsid

RSID bursts heard in the passband, mode and frequency, without switching the modem (needs the rsid-hits patch in patches/)

fldigi_call

escape hatch — call any method by name, incl. future ones

Use application → list_methods to enumerate every method the running build supports. On 4.2.13 all of them are surfaced in a group; fldigi_call is for methods a newer fldigi may add before this connector catches up.

Configuration

Variable

Default

Purpose

FLDIGI_HOST

127.0.0.1

fldigi XML-RPC host

FLDIGI_PORT

7362

fldigi XML-RPC port

FLDIGI_CALLSIGN

(empty)

Operator callsign. The single transmit gate — set it to enable transmit; blank keeps the station receive-only

FLDIGI_BAND_GUIDANCE

off

Experimental advisory band guidance. on to enable

FLDIGI_REGION

2

IARU region for band guidance: 1, 2, or 3

FLDIGI_PATH

(auto)

Explicit path to the fldigi executable (for application launch)

FLDIGI_AUDIO_DEVICE

(system default)

Input device the signal hunt taps: the name (or part of it) of the device fldigi listens on, e.g. iMic

FLDIGI_HUNT_URL

(empty)

URL of a fldigi-mcp-tap running beside fldigi, e.g. http://127.0.0.1:7365, for when this server cannot open the sound card (sandbox, or fldigi on another machine). Blank taps the local input device

In the packaged desktop connector these appear as a settings form — most users only ever fill in the callsign.

Transmit safety

The callsign is the single transmit gate. Keying operations (transmit tx/tune/run_macro/send, and the wefax/navtex send operations, and any keying method via fldigi_call) refuse unless FLDIGI_CALLSIGN is set. With it blank, the station is receive-only. rx, abort, and disable_tx are always allowed because they take the station off the air. Any non-blank value is accepted (club, event, vanity, portable, and international calls all work). See docs/install-and-safety.md.

Band Guidance (experimental, off by default)

An optional, advisory feature that suggests a mode's customary "watering hole" and warns when a frequency falls outside the digital band segment — guidance and defaults, never hard locks. Region-aware (IARU R1/R2/R3), covering 160 m – 70 cm. Enable with FLDIGI_BAND_GUIDANCE=on. It adds the band_guidance tool and enriches modem/frequency set operations with an advisory guidance field. Because band-plan data is hard to get exactly right, it ships experimental and disabled by default. Design and data: docs/band-guidance.md.

Remote / distributed setups

fldigi need not run on the same machine. Point the server at it with FLDIGI_HOST/FLDIGI_PORT. The fldigi machine must be launched with --xmlrpc-server-address 0.0.0.0 to accept LAN connections, and the link should be kept on a trusted LAN or tunneled over SSH (the XML-RPC interface is unauthenticated).

Sandboxed MCP clients (e.g. Claude Desktop): the client runs the connector sandboxed so it can only reach 127.0.0.1, not LAN addresses — so a correct LAN IP for fldigi will time out even though telnet to it works. Use the standalone mcp-host-bridge relay on the client computer (it knows fldigi = port 7362), then set FLDIGI_HOST=127.0.0.1:

pipx install mcp-host-bridge             # or download a binary from its releases
mcp-host-bridge install fldigi --to 192.168.1.50

Manage it with mcp-host-bridge status fldigi / uninstall fldigi. The same tool also bridges N3FJP (for the sibling n3fjp-mcp) and any other local service.

Skills

The skills/ directory contains agent skills — operating procedures distilled from live on-air use — bundled with the repo and the .mcpb package:

  • signal-hunting — find a station worth working the way an operator reads the waterfall: signal_hunt names each signal's mode from its bandwidth and tone grid (RTTY, CW, PSK, Olivia, MFSK, DominoEX, MT63; signatures checked against sigidwiki.com), ranks the one that sits still and calls CQ, tune_to sets modem and carrier, and twenty seconds of text confirms it. Needs pip install 'fldigi-mcp[hunt]' (numpy, sounddevice) and the Audio input device setting; where the server does not run beside the receiver (sandbox, remote fldigi), fldigi-mcp-tap runs there and the server asks it over HTTP (Signal-hunt tap URL); without any audio it falls back to stepping fldigi's search_up. Verified on five recordings of known mode, 5 of 5. Receive only.

  • fldigi-operating — TX/RX handoff done right (^r return-to-receive via transmit → send, abort as the panic button, never poll the TX buffer), RX-buffer polling discipline (delta reads, the no-echo rule, restart detection), and a reference CQ loop. Field-proven during ARRL Field Day 2026.

The fldigi-mcp Operating Field Guide (PDF) documents these skills and their companion contest-operating from the sibling n3fjp-mcp — skills at a glance, installation, a plain-language "Your first session — Claude for hams" chapter for operators new to AI, the operating standard, the special-case playbook, and worked examples transcribed from ARRL Field Day 2026.

In the Claude desktop app and Cowork, upload the skill files as described under Add the operating skills. In Claude Code, copy the skill directory into your ~/.claude/skills/ (or a project's .claude/skills/).

Development

uv sync
uv run ruff check .      # lint
uv run pytest            # tests (no running fldigi required)

The test suite covers the band-plan logic and the operation maps / type coercion; it does not require a running fldigi.

License

GPL-3.0-or-later © 2026 Stefan Brunner (AE5VG)

fldigi-mcp is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. It was MIT-licensed through 0.2.2; the change to GPL-3.0-or-later (the licence fldigi itself uses) lets this project reuse fldigi code, such as its multi-channel signal browser, directly. Talking to fldigi over XML-RPC never required this; porting its decoders does.

Available Tools

22 tools
applicationC

The fldigi program and its process.

Info operations: version, version_struct, name, name_version, config_dir, list_methods. Process operations: launch, stop, terminate, is_running.

launch starts fldigi pointed at the configured XML-RPC endpoint; stop/ terminate ask it to quit (saving options; optionally the log/macros) and fall back to ending a process this server started.

Inputs: operation (required), save_log, save_macros.

band_guidanceA

Advisory band guidance (experimental, region-aware) — informational / QSY help only.

operations:

  • lookup (frequency_hz, optional mode): what the band plan says at a frequency.

  • watering_hole (mode, optional band): the preferred calling frequency for a mode.

  • move_to_watering_hole (mode): set the dial to that frequency (does NOT transmit).

Inputs: operation (required), band, mode, frequency_hz.

browserA

fldigi's Signal Browser over XML-RPC: every station the multi-channel decoder bank has locked to in the passband, with the text decoded on each channel. This is what the left-hand browser panel shows, and it copies stations far too weak for the waterfall to show. operations: channels (list of {channel, freq, active, text}; text accumulates since the last clear, a newline marks a lost-and-regained signal), clear, available.

Runs for PSK, RTTY and CW modems (fldigi's browser covers those). Needs a fldigi built with the patch in fldigi-mcp/patches; stock 4.2.13 has no browser.* methods, and then this tool says so instead of failing. Receive only.

Inputs: operation.

controlsC

fldigi operating controls (the AFC / SQL / Rev / Lock / RxID / TxID buttons) and status. operations: get/set/toggle_afc, get/set/toggle_squelch (SQL), get/set/inc_squelch_level, get/set/toggle_reverse (Rev), get/set/toggle_lock (Lock), get/set/toggle_rxid (RxID), get/set/toggle_txid (TxID), get_status1, get_status2, get_trx_status, get_trx_state.

Inputs: operation (required), value.

diagnosticsA

Host + network diagnostics for troubleshooting connectivity.

Does NOT connect to fldigi. Reports the resolved FLDIGI_HOST/PORT, this process's Python and hostname, the transmit-gate state, and the host's network interfaces — so you can tell whether the process can even see the target's network (e.g. when running host-side vs. sandboxed). If a non- loopback host times out, see mcp-host-bridge (docs/INSTALL.md).

Inputs: no named parameters.

fldigi_callA

Escape hatch: call ANY fldigi XML-RPC method by dotted name (e.g. 'rig.get_mode').

Use station with operation 'list_methods' to discover every method the running build supports. Keying methods remain callsign-gated.

Inputs: method (required), params.

flmsgB

flmsg (message forms) interworking. operations: online, available, transfer, squelch, get_data (RX data since the last query).

These signal or hand data to a running flmsg; none of them key the transmitter.

Inputs: operation (required).

frequencyC

RF frequency and waterfall sideband. operations: get, set (value=Hz), increment (value=Hz), get_sideband, set_sideband (value='USB'|'LSB').

Inputs: operation (required), value.

ioC

ARQ / KISS I/O port. operations: in_use (which port is active), enable_kiss, enable_arq.

Inputs: operation (required).

legacyA

Deprecated fldigi methods, kept so the whole catalog is reachable. Each has a current equivalent, which you should prefer: get/set_sideband -> frequency get/set_sideband; rsid -> controls toggle_rxid; get/set_rig_name, get/set_rig_frequency, get/set_rig_mode(s), get/set_rig_bandwidth(s) -> the rig tool; log_get_sideband -> frequency get_sideband; flmsg_online/available/transfer/squelch -> the flmsg tool.

Inputs: operation (required), value.

logA

Logbook (QSO / contest) fields. operations: get (field=...), set (field=..., value=...), clear, last_record, all_records.

Settable fields: call, name, qth, locator, serial_number, exchange, rst_in, rst_out, contest_counter (set only: the starting contest serial number). Gettable fields also include frequency, time_on/off, serial_number_sent, state, province, country, band, notes, az. last_record / all_records return ADIF.

Inputs: operation (required), field, value.

modemC

Operating mode (the fldigi "Op Mode" menu) and modem settings. operations: get, list, get_id, get_max_id, set (value=mode name e.g. 'BPSK31'), set_by_id (value=id), get_io_names (modems usable for KISS/ARQ I/O), get/set/inc_carrier, get/set/inc_afc_range, get/set/inc_bandwidth, get_quality, search_up, search_down, olivia_get/set_bandwidth, olivia_get/set_tones.

Inputs: operation (required), value.

rigA

Rig (CAT) control via flrig/Hamlib/RigCAT. operations: get/set_name, get/set_frequency (value=Hz), get/set_mode (value=name), get_modes, set_modes (value=[...]), get/set_bandwidth, get_bandwidths, set_bandwidths (value=[...]), get/set_notch, enable_qsy (value=1|0), set_smeter / set_pwrmeter (value=int, drives fldigi's meter display).

Inputs: operation (required), value.

rsidB

RSID bursts the detector heard: which modes were announced in the passband and where, as {utc, mode, hz} entries since the last clear. Works with fldigi's RSID set to notify-only (RxID on, "do not change modem"), so the current modem keeps decoding while the list tells you what else is on. operations: hits, clear, available.

Needs a fldigi built with the rsid-hits patch in fldigi-mcp/patches; on stock 4.2.13 the tool says so instead of failing. Receive only.

Inputs: operation.

signal_huntA

Find and name the signals in the receiver audio and rank them the way a contest operator reads the waterfall: the station that sits still and calls CQ scores highest.

method 'audio' (default): tap seconds of audio from the input device (FLDIGI_AUDIO_DEVICE, the device fldigi listens on; or device as a name substring or index; wav analyses a file instead). Needs the optional extra: pip install 'fldigi-mcp[hunt]'. method 'devices': list the input devices the tap can open. method 'browser': read fldigi's Signal Browser (needs the browser patch, see the browser tool): one candidate per channel the decoder bank holds, with its text, for the current modem family (PSK, RTTY or CW). Finds stations the spectrum analyser ranks near the floor, but names no mode: it reports what fldigi is set to. method 'api': blind fallback with no audio access; steps modem.search_up across the passband for each modem (mode='RTTY,BPSK31,...') and reads modem.get_quality. Slow.

Each candidate carries carrier_hz, mode (RTTY with shift, CW, BPSK31/63/125, Olivia with tones and bw, MFSK16, DominoEX, MT63, or unknown), db_over_floor, persistence (fraction of the window it was present), periodicity (a CQ loop repeats), score, and fldigi_modem, the name tune_to needs. Nothing here transmits.

Inputs: top, wav, mode, device, +2 more.

spotC

Spotting / PSK Reporter. operations: get_auto, set_auto (value=bool), toggle_auto, pskrep_count.

Inputs: operation (required), value.

statusB

Snapshot: version, modem, frequency (Hz), TX/RX state, transmit gate, region, band.

Inputs: no named parameters.

textC

RX/TX text and data. operations: read (decoded RX text; start/length), rx_length, get_rx (value=[start, length], the raw byte range), clear_rx, add_tx (value=text), add_tx_queue, add_tx_bytes (value=text or bytes), clear_tx, get_rxtx_data, get_rx_data, get_tx_data.

add_tx / add_tx_bytes only stage text in the TX widget; they do not transmit.

Inputs: operation (required), start, value, length.

transmitA

Transmitter control. operations: tx, tune, rx, abort, disable_tx, enable_tx, run_macro (value=id), get_max_macro_id, send (text=...), and timing information: tx_timing (value=test string), char_rates, char_timing (value=one character); both timings return 'samples : sample rate : seconds'.

Keying operations (tx, tune, run_macro, send) require a configured callsign; rx, abort, disable_tx and the timing operations never key and are always allowed. send queues text and transmits, auto-returning to receive by default.

Inputs: operation (required), text, value, return_to_rx.

tune_toA

Set fldigi to a signal_hunt candidate: modem by fldigi name (e.g. 'RTTY', 'BPSK31', 'OLIVIA-8/250', 'MFSK16', 'DOMEX11', 'MT63-500'), the audio carrier, AFC on, and RxID off by default so another station's RSID burst cannot retune the modem mid-pass. Read the result with text read after 20 seconds; modem get_quality says whether it locked. Does not transmit.

Inputs: carrier_hz (required), fldigi_modem (required), afc, rxid.

wefaxC

WEFAX (weather fax) mode. operations: state, skip_apt, skip_phasing, tx_abort, end_reception, start_manual_reception, set_adif_log (value=bool), set_max_lines (value=int), get_received_file (value=timeout), send_file (value=[filename, timeout_seconds]).

send_file transmits and is callsign-gated.

Inputs: operation (required), value.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 22 tools

    Disambiguation2/5

    Several tools overlap in triggering technical operations (e.g., 'legacy' deprecated methods mixed with 'fldigi_call' escape hatch and 'transmit' keying operations create ambiguity about which to use). Additionally, 'controls' vs 'status' fields are not clearly delineated from 'application' info operations, and 'signal_hunt' and 'browser' both serve signal detection, though with different methods.

    Naming Consistency2/5

    Naming is inconsistent: some tools use single-word verbs (status, legacy, transmit, rig, log, text) while others use compound nouns (signal_hunt, tune_to, band_guidance, wefax, navtex). Operations within tools are mostly verb_noun (get/set/toggle) but the tool-level names mix styles, and 'legacy' is a category name not a clear action.

    Tool Count3/5

    22 tools is on the higher side but not extreme, given fldigi's broad feature set (transmit, rig, modem, log, text, special modes). However, some tools like 'legacy' and 'fldigi_call' add bulk without distinct value, making the count feel heavier than needed; a leaner set around 15 would be more appropriate.

    Completeness4/5

    The server covers core fldigi operations well: transmit, receive, modem control, frequency, log, text, rig, special modes (WEFAX, NAVTEX), and diagnostics. Minor gaps include lack of a direct receive-while-transmitting control, but the 'transmit' send with auto-return and 'text' read cover most workflows. The presence of 'legacy' and 'fldigi_call' suggests full reachability, but they are fallback rather than missing functionality.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      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
      85 PyPI
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables logging amateur-radio QSOs to N3FJP logging software via MCP tools, including automatic logging, dupe checking, and band/mode management.
      10
      167 PyPI
      MIT
    • 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
      163 PyPI
      1
      MIT