Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Fldigi MCP

by sbrunner-atxversion 0.4.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.sbrunner-atx/fldigi-mcp

How to install

What it does

Control fldigi (amateur-radio digital modes) over XML-RPC: modem, frequency, rig, log, transmit.

  • Connects Runs on your computer
  • Account or key No key needed · 1 setting to fill in (FLDIGI_CALLSIGN)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score12/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Fldigi MCP. Follow https://mcp.popnx.com/i/sbrunner-atx-fldigi-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Fldigi MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "fldigi": { "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.

    Descriptions are as written by the maker.

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "fldigi": {
          "command": "uvx",
          "args": [
            "fldigi-mcp"
          ],
          "env": {
            "FLDIGI_CALLSIGN": "your-value"
          }
        }
      }
    }
  5. Quit Claude and open it again

  6. Try it

    Use Fldigi MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1
  • FLDIGI_PORT fldigi XML-RPC port. · default 7362
  • FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default off
  • FLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Fldigi MCP yet

Fldigi MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Fldigi MCP

  • 1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • 1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)
  • 1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)
  • 1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Fldigi MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.

    Descriptions are as written by the maker.

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcp
  5. Type /mcp in Claude Code

    You should see Fldigi MCP listed as connected

  6. Try it

    Use Fldigi MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1
  • FLDIGI_PORT fldigi XML-RPC port. · default 7362
  • FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default off
  • FLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Fldigi MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "fldigi": { "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.

    Descriptions are as written by the maker.

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Fldigi MCP settings, FLDIGI_CALLSIGN is empty; add your key and save

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Fldigi MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1
  • FLDIGI_PORT fldigi XML-RPC port. · default 7362
  • FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default off
  • FLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

1 setting(s) to fill in (FLDIGI_CALLSIGN) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Fldigi MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "fldigi": { "type": "stdio", "command": "uvx", "args": [ "fldigi-mcp" ], "env": { "FLDIGI_CALLSIGN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For FLDIGI_CALLSIGN, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Fldigi MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • FLDIGI_CALLSIGN Operator callsign. Required to enable transmit; leave blank to stay receive-only.

    Descriptions are as written by the maker.

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Fldigi MCP settings, FLDIGI_CALLSIGN is empty; add your key and save

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Fldigi MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Fldigi MCP or shows a Fldigi MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • FLDIGI_HOST fldigi XML-RPC host. · default 127.0.0.1
  • FLDIGI_PORT fldigi XML-RPC port. · default 7362
  • FLDIGI_BAND_GUIDANCE Enable experimental advisory band guidance (on/off). · default off
  • FLDIGI_REGION IARU region for band guidance: 1, 2, or 3. · default 2

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Fldigi MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user fldigi --env FLDIGI_CALLSIGN=your-value -- uvx fldigi-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "fldigi": {
      "command": "uvx",
      "args": [
        "fldigi-mcp"
      ],
      "env": {
        "FLDIGI_CALLSIGN": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "fldigi": {
      "command": "uvx",
      "args": [
        "fldigi-mcp"
      ],
      "env": {
        "FLDIGI_CALLSIGN": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "fldigi": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "fldigi-mcp"
      ],
      "env": {
        "FLDIGI_CALLSIGN": "your-value"
      }
    }
  }
}

Values you fill in

  • FLDIGI_CALLSIGN required env
    Operator callsign. Required to enable transmit; leave blank to stay receive-only.
  • FLDIGI_HOST env
    fldigi XML-RPC host.
  • FLDIGI_PORT env
    fldigi XML-RPC port.
  • FLDIGI_BAND_GUIDANCE env
    Enable experimental advisory band guidance (on/off).
  • FLDIGI_REGION env
    IARU region for band guidance: 1, 2, or 3.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
41/wk
Licencei
GPL-3.0
Connection
Runs on your computer
Latest versioni
0.4.1
Categoryi
Other
Published to registryi
Nov 13, 2026
Code last changedi
Nov 13, 2026
Maker
sbrunner-atx
Packages
pypi: fldigi-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account sbrunner-atx, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 6 days ago

  • ✓ Pass

    Has a licence

    Uses GPL-3.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for fldigi-mcp@0.4.1

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/sbrunner-atx-fldigi-mcp.svg)](https://mcp.popnx.com/en/servers/sbrunner-atx-fldigi-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20815 servers in this category
  • Published to the registry more recently than 87% of the other 20815 servers in this category
  • Basic checks equal to or better than 99% of the other 20815 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fldigi MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 6 days ago, and the latest version (0.4.1) reached the registry 6 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Fldigi MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseGPL-3.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](https://github.com/sbrunner-atx/fldigi-mcp/blob/main/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](https://github.com/sbrunner-atx/fldigi-mcp/blob/main/docs/fldigi-api.pdf) — the same, as a printable PDF.
  • [docs/fldigi-api-spec.md](https://github.com/sbrunner-atx/fldigi-mcp/blob/main/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.

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](https://docs.astral.sh/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](https://github.com/sbrunner-atx/fldigi-mcp/blob/main/docs/INSTALL.md). 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.

ToolControls (fldigi area)
statusquick snapshot: version, mode, frequency, T/R, callsign, band
diagnosticshost/network info for connectivity troubleshooting (no fldigi connection)
applicationprogram info + launch/stop the fldigi process (fldigi.*)
modemOp Mode / modem select, carrier, bandwidth, AFC range, Olivia
frequencydial frequency and waterfall sideband
controlsAFC, SQL, Rev, Lock, RxID, TxID, status fields
transmitT/R, Tune, abort, disable/enable Tx, macros, send — callsign-gated
rigCAT control: mode, frequency, bandwidth, notch, QSY, meters
logLogbook / contest fields; ADIF last/all records
textRX/TX text and data streams
spotspotting / PSK Reporter
wefaxWEFAX (weather fax) mode
navtexNAVTEX / SitorB mode
flmsgflmsg (message forms) interworking
ioARQ / KISS I/O port selection
legacydeprecated methods fldigi still serves, each with its current equivalent named
band_guidanceadvisory band/watering-hole help (experimental)
signal_huntfind and name the signals in the receiver audio; rank CQing stations (experimental, [hunt] extra)
tune_toset modem and carrier to a signal_hunt candidate, receive only
browserfldigi's Signal Browser: every station the decoder bank holds, with its text (needs the fldigi patch in patches/)
rsidRSID bursts heard in the passband, mode and frequency, without switching the modem (needs the rsid-hits patch in patches/)
fldigi_callescape 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

VariableDefaultPurpose
FLDIGI_HOST127.0.0.1fldigi XML-RPC host
FLDIGI_PORT7362fldigi 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_GUIDANCEoffExperimental advisory band guidance. on to enable
FLDIGI_REGION2IARU 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

Only the beginning is shown; read the rest in the repo