Skip to main content

n1mm-mcp

PyPI MCP Registry

MCP server for N1MM Logger+: live contest state — station, QSOs, bandmap, score and rate, multipliers, and contest clock — through any MCP-compatible AI assistant.

Data from N1MM Logger+'s UDP broadcasts on your local network. Part of the qso-graph project. No authentication required.

Install

uvx n1mm-mcp            # run it; nothing to install

Tools

Tool Description Key Parameters
n1mm_current_state Station snapshot: connection, contest, operator, radios station_name
n1mm_lookup The callsign being entered (pre-log) plus current band and mode station_name
n1mm_contacts QSO log: recent contacts, edits and deletes count, since, band, mode, call_pattern
n1mm_bandmap Live spots, multiplier targets, band activity band, mode, callsign, mults_only
n1mm_performance Score, rate, bands, run/S&P, hourly timeline band, mode
n1mm_multipliers Multiplier grid, needs, value analysis band
n1mm_clock Contest timing, off-time, pacing duration_hours, target_score, target_qsos, min_gap_minutes
n1mm_diagnostics Server health, parse errors, memory station_name
get_version_info Service version + upstream spec version (fleet identity attestation) —

Every tool takes an optional station_name for multi-station setups (SO2R, multi-op).

What is N1MM Logger+?

N1MM Logger+ is a Windows contest logger. It can broadcast its state over UDP: contacts, spots, radio info and score. n1mm-mcp listens to those broadcasts and keeps the contest state in memory, so an assistant can answer questions about it. N1MM doesn't know it's there.

N1MM Logger+ (Windows)
    │ UDP broadcast (port 12060, XML)
    ▼
n1mm-mcp (Python: the same PC, or any OS on the LAN)
    ├── UDP listener (background)
    ├── State engine (in memory, per StationName)
    │   MCP protocol (stdio)
    ▼
AI assistant

Quick Start

Turn on N1MM's broadcasts

  1. In N1MM: Config → Configure Ports → Broadcast Data, and enable all message types.
  2. Set the destination to 127.0.0.1:12060, N1MM's address for "this PC". n1mm-mcp listens there by default, and nothing outside the PC can reach it.

N1MM on another PC

Run n1mm-mcp with --bind 0.0.0.0 (every network interface) or --bind <this PC's LAN address>, and point N1MM at it: this PC's address (192.168.1.20:12060), or your subnet's broadcast address (192.168.1.255:12060) to reach every PC on it. N1MM accepts several destinations separated by spaces. Don't use 255.255.255.255: N1MM's own documentation warns that it risks broadcasting to the internet (N1MM: External UDP Broadcasts).

Listening on the network means any device on it can send n1mm-mcp packets, so only do it on a network you trust.

Configure your MCP client

n1mm-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": {
    "n1mm": {
      "command": "uvx",
      "args": ["n1mm-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

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

ChatGPT Desktop

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

Cursor

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

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

VS Code / GitHub Copilot

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

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

Gemini CLI

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

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

Ask questions

"What's my rate over the last hour?"

"Which multipliers do I still need on 20m?"

"Is the station on the bandmap a new multiplier?"

"How much off-time have I used, and am I on pace for my target?"

"Show me the last 10 QSOs."

CLI Options

Option Default Description
--port 12060 UDP listen port
--bind 127.0.0.1 Address to listen on; 0.0.0.0 for N1MM on another PC
--transport stdio MCP transport (stdio or streamable-http)
--heartbeat-timeout 60 Seconds before the connection goes stale
--stale-timeout 900 Seconds before the connection goes disconnected
--max-spots 2000 Maximum spots in the bandmap buffer
--spot-ttl 30 Spot time-to-live in minutes

Testing Without N1MM

N1MM_MCP_MOCK=1 n1mm-mcp

MCP Inspector

n1mm-mcp --transport streamable-http

Then open the MCP Inspector at http://localhost:8008.

Development

git clone https://github.com/qso-graph/n1mm-mcp.git
cd n1mm-mcp
uv sync --group dev
uv run pytest

License

GPL-3.0-or-later

Metadata

Release files for n1mm-mcp 0.1.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for n1mm-mcp 0.1.7
File Size Uploaded
n1mm_mcp-0.1.7.tar.gz 156.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for n1mm-mcp 0.1.7
File Interpreter ABI Platform
n1mm_mcp-0.1.7-py3-none-any.whl Python 3 none any Details

Total release size: 191.8 kB

Release files / n1mm_mcp-0.1.7.tar.gz

Download URL n1mm_mcp-0.1.7.tar.gz
Size 156.4 kB
Tags Source
SHA-256 checksum
How to use checksums
5bb964ebf2a2e6670a9195e4bdf113ea7ec3e32efd1ceb1a620c30d4a9aa1e67
BLAKE2b-256 checksum
How to use checksums
1e917a6971061b32dbbdc97ef8dd9eccde0e6723397171eb9a1d8479d1e17d75
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Release files / n1mm_mcp-0.1.7-py3-none-any.whl

Download URL n1mm_mcp-0.1.7-py3-none-any.whl
Size 35.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ac1f7e753fd49450033743b9c167359458ebff8ee2749927f031954c12bc19f7
BLAKE2b-256 checksum
How to use checksums
410a580272c515b7b308209312150aa1f9f818b601983fb5bb64774024066466
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.1

2 release files

0.2.0

2 release files

0.1.8

2 release files

This release

0.1.7 This release

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page