Skip to main content
Glama
netlogger-mcp

netlogger-mcp

by qso-graph

netlogger-mcp

PyPI MCP Registry

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

Related MCP server: lotw-mcp

Tools

Tool

Description

Key Parameters

netlogger_active_nets

Nets on the air now: frequency, band, mode, net control, logger, monitoring count

name_like

netlogger_checkins

A live net's check-in list, plus the pointer (the station being worked now)

server_name, net_name

netlogger_past_nets

Closed nets over the last N days, with the net IDs past check-ins need

interval_days, name_like

netlogger_past_checkins

A closed net's check-in list

server_name, net_name, net_id

netlogger_set_callsign

Save your callsign (asked once, on first use)

callsign

get_version_info

Service version + upstream spec version (fleet identity attestation)

—

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 Neighbor 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:

Measure

Detail

NetLogger's call limits

GetActiveNets 1/min, GetCheckins 3/min, GetPastNets 1/min, GetPastNetCheckins 10/min. Checked before a request is sent, never after.

One budget per user

Every copy you run (Claude Desktop, Claude Code, a script) shares one budget, through a locked file beside settings.json.

Shared answers

Every copy also shares the answers it fetched, so a copy that has hit the limit gets another copy's recent answer, with its age, instead of an error.

Response caching

Active nets 60 s, check-ins 20 s, past nets 60 s, past check-ins 1 hour. Filtering by name costs no extra calls.

How old an answer is

Every answer has as_of_utc (when it was given) and age_seconds (how old the data is), so it was fetched at as_of_utc minus age_seconds.

Stale answers over errors

When a limit is reached, the last answer comes back with its age rather than a new request.

429 back-off

A "too many requests" on any call stops all calls for at least a minute, longer if NetLogger asks.

Past-net windows

More than 7 days of past nets needs a name filter, NetLogger's rule to protect its server.

Request timeout

15-second timeout.

User-Agent header

Every request names this project and your callsign, so NetLogger's operators can see who is asking.

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 (for example, 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.

Available Tools

6 tools
get_version_infoGet Version InfoA
Read-onlyIdempotent

Get netlogger-mcp's version, the NetLogger API version it is built for, and the version of the records it returns.

Inputs: no named parameters. Returns: object

netlogger_active_netsNetlogger Active NetsA
Read-onlyIdempotent

List nets on the air now.

Inputs: name_like. Returns: object

netlogger_checkinsNetlogger CheckinsA
Read-onlyIdempotent

Get a live net's check-in list, and the pointer: the serial number of the station net control is working now.

Inputs: net_name (required), server_name (required). Returns: object

netlogger_past_checkinsNetlogger Past CheckinsB
Read-onlyIdempotent

Get a closed net's check-in list.

Inputs: net_id (required), net_name (required), server_name (required). Returns: object

netlogger_past_netsNetlogger Past NetsA
Read-onlyIdempotent

List closed nets over the last few days, with the net IDs netlogger_past_checkins needs.

Inputs: name_like, interval_days. Returns: object

netlogger_set_callsignNetlogger Set CallsignA
Idempotent

Save the user's amateur radio callsign. Needed once, before the first lookup.

NetLogger is told which station is asking, in every request, so it can tell one user from another. Ask the user for their own callsign; don't guess it.

Inputs: callsign (required). Returns: object

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    The active/past net and active/past check-in pairs are the only potential confusion points, but descriptions explicitly say "live" vs "closed," so an agent can choose correctly. get_version_info and netlogger_set_callsign are clearly separate from the lookup tools.

    Naming Consistency4/5

    Five tools use clean snake_case and four share a netlogger_ prefix, forming a readable family. Minor deviations: get_version_info drops the prefix, and set_callsign is the only verb-first name while the rest are adjective_noun.

    Tool Count5/5

    Six tools is well-scoped for a focused read-only NetLogger client, with one tool per operation. Nothing feels padded or missing at this size.

    Completeness4/5

    The core lifecycle is covered: set callsign, discover live/past nets, and pull live/past check-in lists with the pointer for current activity. Minor gaps: no net metadata (frequency, net control) or per-station history beyond the raw check-in list, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for ARRL Logbook of The World (LoTW) that enables querying confirmations, uploaded QSOs, DXCC credits, and user activity through any MCP-compatible AI assistant. Part of the qso-graph project, it is read-only and requires LoTW credentials for authenticated tools.
      6
      75 PyPI
      1
      GPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides read-only access to cached metadata of public activities, contests, and competitions from multiple sources via SQLite, enabling search and listing without hitting external sites.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves read-only archived ResMed CPAP data from a local SQLite database, enabling MCP clients to query nightly summaries, raw signals, and sync status over the LAN.
      77 npm
      MIT