Netlogger MCP

netlogger-mcp

MCP server for NetLogger: nets on the air now, live check-in lists and who's up, and past nets and their check-ins, through any MCP-compatible AI assistant.

Data from NetLogger's public XML Data Service (API 1.3). Part of the qso-graph project. No API key needed. Your callsign is asked for once (see below).

Install

uvx netlogger-mcp            # run it; nothing to install

Tools

What is NetLogger?

NetLogger is the logging program many amateur-radio nets use: net control or a logger keeps the check-in list, and anyone can follow the net live. Its server publishes active nets, check-in lists and past nets through a public API.

Your Callsign

Every request tells NetLogger which station is asking, so it can tell one user from another:

netlogger-mcp/<version> (KI7MT; +https://github.com/qso-graph/netlogger-mcp)

The version is the installed one — it is read from the package, not written here.

On first use the assistant asks for your callsign and saves it. You're asked once. To set it yourself, use NETLOGGER_MCP_CALLSIGN=KI7MT.

It's saved in settings.json, in ~/.config/netlogger-mcp/ (Linux), ~/Library/Application Support/netlogger-mcp/ (macOS) or %APPDATA%\netlogger-mcp\ (Windows).

Good Neighbour Policy

NetLogger is a donation-funded service on one server, and it limits how often each call may be made. We keep to those limits:

Bands and Frequencies

NetLogger's band and frequency are whatever the logger typed ("40M", "75M", "DMR", "7033", "3918 KHz", "147.030 91.5", "TG 3141"). They're returned as typed, and beside them, only when the text can be read reliably: frequency_mhz, band_adif (the ADIF band, from ADIF 3.1.7's Band enumeration), tone_hz and talkgroup. A frequency outside the amateur bands (e.g. GMRS) gets no band_adif.

Privacy

NetLogger's check-in data includes street addresses and ZIP codes, and past nets include the IP address of whoever opened them. None of these are ever returned.

Quick Start

Configure your MCP client

netlogger-mcp works with any MCP-compatible client. Add the server config and restart. The tools appear automatically.

Claude Desktop

Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):

{

"mcpServers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

Claude Code

Add to .claude/settings.json:

{

"mcpServers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

ChatGPT Desktop

{

"mcpServers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

Cursor

Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):

{

"mcpServers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

VS Code / GitHub Copilot

Add to .vscode/mcp.json in your workspace:

{

"servers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

Gemini CLI

Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):

{

"mcpServers": { "netlogger": { "command": "uvx", "args": ["netlogger-mcp"] } } }

Ask questions

"What nets are on the air right now?"

"Are any 80m nets running?"

"Who's checked into the county ARES net, and who's up now?"

"Which nets ran in the last three days?"

"Show me the check-ins from last night's net."

As a Python Library

The same code works without an AI, with the same limits and cache. A library can't ask for your callsign, so you pass it in:

from netlogger_mcp.netlogger import NetLoggerSource

nl = NetLoggerSource(callsign="KI7MT") for net in nl.active_nets()["nets"]: live = nl.checkins(net["server"], net["name"]) print(net["name"], "up now:", live["pointer_callsign"])

Apps can also name themselves, using ADIF's PROGRAMID and PROGRAMVERSION: NetLoggerSource(callsign="KI7MT", program_id="MyLogger", program_version="1.0").

Testing Without Network

NETLOGGER_MCP_MOCK=1 netlogger-mcp

MCP Inspector

netlogger-mcp --transport streamable-http --port 8014

Development

git clone https://github.com/qso-graph/netlogger-mcp.git

cd netlogger-mcp uv sync --group dev uv run pytest

License

GPL-3.0-or-later. adif_band.json is the ADIF 3.1.7 Band enumeration, the work of the ADIF Developers Group (adif.org.uk), included unchanged.