AE5VG

AE5VG · Austin, TX · Amateur Radio + AI

An AI assistant that can work the bands with you.

Open-source MCP connectors put fldigi, WSJT-X and N3FJP under the control of an AI assistant such as Claude: a growing toolset for AI-assisted amateur radio communication.

From Field Day 2026: a BPSK31 exchange as decoded, garble included, callsigns anonymized. The assistant was at the keyboard; the notes in gray are what it observed.

TX CQ FD CQ FD de K6ABC K6ABC pse k RX K6ABC de W7XYZ 1D AZ; 1D AZ PSE K caller sent callsign and full exchange up front; no need to ask TX W7XYZ de K6ABC K6ABC · Pse copy 2A 2A STX STX · de K6ABC BK RX K6ABC QSL TU 73 de W7XYZ · GL es 73 · sk TX QSL 1D AZ TU W7XYZ de K6ABC GL FD sk sk logged while the TU was still transmitting

Why

One of the most interesting things AI can do is operate autonomously in fuzzy environments. We have self-driving cars in messy city traffic, drones that find their own targets, lawn mowers that know where the lawn ends and the flower bed begins.

Radio communication is fuzzy by its very nature. Humans talk outside of fixed schemas, and antennas, power, band conditions and QRM all alter what the receiver sees. Wireless communication has used error correction for decades, but that works by transmitting redundant information and using math to reconstruct the message, or to request it again. The challenge here is different: have an AI carry a QSO the way a human does, preferably in a way that appears human on the receiving end.

Skeptics will say Part 97 requires human operators. Not quite: it requires operator supervision, and machine communication has plenty of precedent, from Wi-Fi to FT8 to self-announcing beacons. Does autonomous operation not defeat the point of a hobby built on human operators? Anyone who has been in this hobby for decades knows it is mostly about the tinkering: once the new rig is going and the antenna is perfect, we move on to the next shiny thing. This project is not about replacing human operators. It is about experimenting and demonstrating what is possible.

I started this project in 2026, preparing for Field Day, as a simple proof of concept. It worked: we operated the very first autonomous QSO in history, with me as the licensed operator at the radio, ready to take over at any moment.

Agentic Connectors

At its core are three Model Context Protocol (MCP) connectors. MCP servers are for AI what drivers are for hardware: they let an AI talk to the real world, to software, or even to a radio.

Connector · GPL-3.0

fldigi-mcp

The most powerful of the three. An AI can control every aspect of fldigi, in both directions, and by proxy any rig fldigi is set up to control. Safeguarded against accidental AI-initiated transmissions.

fldigi-mcp →
Connector · MIT

wsjtx-mcp

The little sister. FT8 and its siblings are automated protocols to begin with, but now an AI can run the whole process of initiating and completing QSOs through WSJT-X.

wsjtx-mcp →
Connector · MIT

n3fjp-mcp

The logging counterpart. It connects to Amateur Contact Log and any of Scott's 200+ contest loggers.

n3fjp-mcp →
Connector · MIT

serial-console-mcp

Originally meant to control the rig directly via serial or USB from the AI. That proved unnecessary: fldigi has rig control built in, and flrig covers the rest. But it can put AI on any device with a serial protocol, from an alarm panel to a large telecom router.

serial-console-mcp →
Utility · MIT

mcp-host-bridge

AI agents run in a sandbox, isolated from the host. If fldigi, WSJT-X or N3FJP run on the same host as the AI, we control them via loopback; if they run on another host, we need to pinch a hole into the sandbox, which is what this tool does.

mcp-host-bridge →

With these tools and some agentic plumbing, an AI can initiate or answer a QSO and log it automatically, all day, while you supervise and enjoy whiskey and cigars.

Receive-only by default

Without a callsign in the settings, none of the connectors can key a transmitter. The assistant can listen, decode and log, but transmitting requires you to put your callsign in the configuration first. You remain the control operator.

What is next

During Field Day, the agentic plumbing was a frontier model, cloud-hosted, which requires an always-on Internet connection. That has three disadvantages: you have to be connected to the Internet to communicate via a radio, which rather defeats the purpose; you are eating up tokens; and frontier models are powerful but slow.

Instead of running a trillion-parameter model, the goal is a small billion-parameter model that can run in the field, on a modern CPU with AI extensions or on an inference processor like those some drones carry. What we need is a purpose-built ham-radio model. Its sole purpose is to understand how humans communicate on the digital modes and to do smart error correction, very much the way our human mind reads the right message out of a partially garbled decode. The first step in building a model from scratch is collecting training data. More on the Ham Radio Model page.

Install

Downloads

The latest release of every module, with the manuals and release notes.

Downloads →
Set up

Getting Started

For a ham who has never used an assistant: from install to the first QSO on a dummy load.

Getting Started →
Read

User Guide

The Field Guides and the API references, online and as PDF.

User Guide →