N1mm Mcp

io.github.qso-graph由 GitHub 账号 qso-graph 发布v0.4.0更新于 Nov 2, 2026

N1MM Logger+ MCP server. Live contest state: QSOs, bandmap, score, rate, multipliers.

已验证STDIO仅桌面位置与生活数据与分析

概览

AI 生成的概览

只读的 MCP 服务器,监听 N1MM Logger+ 的 UDP 广播,让助手获取实时业余无线电比赛状态:通联、波段图、分数、速率和倍数。

可以做什么
  • 读取电台、比赛、操作员与收发机状态,以及服务与规范版本
  • 查询正在输入的呼号(记录前)及当前波段和模式
  • 查看近期通联、修改与删除记录,以及实时波段图 spot 和倍数目标
  • 查看分数、滚动速率、按波段与模式细分、倍数和比赛时钟节奏
  • 查看双机(SO2R)焦点与发射时长、所有联网台站以及 DXpedition 堆积统计
  • 检查服务器健康、解析错误和内存,便于排错
适用场景
在业余无线电比赛期间使用 N1MM Logger+ 时,若想让助手在不离开日志软件的情况下回答速率、所需倍数、休息时间节奏、近期通联或堆积情况等问题,就适合安装。
运行要求
以 Python 包形式本地运行(uvx 或 pip),无需认证、API 密钥或环境变量。N1MM Logger+ 需通过 UDP 广播状态(默认端口 12060),通常在同一台电脑上;若 N1MM 在另一台电脑,需将 --bind 设为本机某个地址,并用 --allow 逐个允许发送方。另有模拟模式可在没有 N1MM 时测试。
安装前请注意
只读:没有任何工具会写入 N1MM、日志或其他内容。UDP 发送方地址可被伪造,允许列表只能挡住其他机器,不能证明数据报来自谁;伪造的数据包可能误导你对比赛状态的判断,因此应把状态视为上报值而非已核实值,并在可信网络中运行。拒绝绑定 0.0.0.0;避免使用 255.255.255.255 广播地址。发射时长仅统计 N1MM 自己键控电台的情况,不含手键或话筒 PTT。

安装

在 SourceWeft 中

  1. 打开 控制台中的 N1mm Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

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

bash
uvx n1mm-mcp            # run it; nothing to install

Tools

ToolDescriptionKey Parameters
n1mm_current_stateStation snapshot: connection, contest, operator, radiosstation_name
n1mm_lookupThe callsign being entered (pre-log) plus current band and modestation_name
n1mm_contactsQSO log: recent contacts, edits and deletescount, since, band, mode, call_pattern
n1mm_bandmapLive spots, multiplier targets, band activityband, mode, callsign, mults_only
n1mm_performanceScore, rate, bands, run/S&P, hourly timelineband, mode
n1mm_multipliersMultiplier grid, needs, value analysisband
n1mm_clockContest timing, off-time, pacingduration_hours, target_score, target_qsos, min_gap_minutes
n1mm_diagnosticsServer health, parse errors, memorystation_name
n1mm_so2rTwo radios: each radio now, transmit/receive focus, same-band warning, transmit time and minutes per band, focus swaps, QSOs per radio and while the other radio runsstation_name
n1mm_networkEvery networked station: operator, radios, rate, idle time, band, shared score per contest call, stations sharing a band and mode, QSOs per operator—
n1mm_pileupDXpedition pileup: rate, unique calls, dupes, continents and countries calling, split, dead airwindow_minutes
get_version_infoService version + upstream spec version (fleet identity attestation)—

Every tool except n1mm_network (which covers all stations) takes an optional station_name for multi-station setups.

Everything comes from N1MM's UDP broadcasts; n1mm-mcp never talks to a radio. N1MM reports transmitting only when it keys the radio itself (macros, its CW keyer), so a paddle or microphone PTT doesn't count as transmit time in n1mm_so2r.

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

Give one address of this PC and name who may send:

bash
n1mm-mcp --bind 192.168.1.20 --allow 192.168.1.40

Then point N1MM at this PC's address (192.168.1.20:12060), or at 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).

--allow is required whenever --bind is a network address, and is repeatable for more than one PC. A datagram from any other address is dropped without being read, and counted — n1mm_diagnostics shows the count and the addresses, so traffic you did not expect is visible rather than silent.

--bind 0.0.0.0 is refused. It listened on every interface at once, including whatever Wi-Fi a laptop happened to be joined to, and it cannot be narrowed afterwards. Name the interface you mean.

What the allow-list does and does not do

A UDP sender's address can be forged by anything on the same network, so the list keeps other machines out; it is not proof of who sent a datagram. What limits the damage is that n1mm-mcp only reads: it has no tool that writes to N1MM, your log, or anything else. A forged packet can therefore mislead you about contest state — a wrong frequency, a spot that was never spotted — but it cannot act, and nothing it contains is written anywhere. Treat the state as reported, not as verified, and run 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):

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

Add to .claude/settings.json:

json
{  "mcpServers": {    "n1mm": {      "command": "uvx",      "args": ["n1mm-mcp"]    }  }}
ChatGPT Desktop
json
{  "mcpServers": {    "n1mm": {      "command": "uvx",      "args": ["n1mm-mcp"]    }  }}
Cursor

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

json
{  "mcpServers": {    "n1mm": {      "command": "uvx",      "args": ["n1mm-mcp"]    }  }}
VS Code / GitHub Copilot

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

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

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

json
{  "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

OptionDefaultDescription
--port12060UDP listen port
--bind127.0.0.1Address to listen on. One address of this PC; 0.0.0.0 is refused
--allowthis PCAn address that may send to us; repeatable. Required with a network --bind
--transportstdioMCP transport (stdio or streamable-http)
--heartbeat-timeout60Seconds before the connection goes stale
--stale-timeout900Seconds before the connection goes disconnected
--max-spots2000Maximum spots in the bandmap buffer
--spot-ttl30Spot time-to-live in minutes

Testing Without N1MM

bash
N1MM_MCP_MOCK=1 n1mm-mcp

MCP Inspector

bash
n1mm-mcp --transport streamable-http

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

Development

bash
git clone https://github.com/qso-graph/n1mm-mcp.gitcd n1mm-mcpuv sync --group devuv run pytest

License

GPL-3.0-or-later

来源:README.md,提交 8b118f8

工具

12

get_version_info

Get Version Info

Get n1mm-mcp service version and upstream UDP contract version. Returns the running PyPI version of n1mm-mcp and the N1MM Logger+ UDP broadcast contract revision in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol. Note: n1mm_diagnostics remains the canonical health probe (heartbeat, parse errors, memory). get_version_info is a lighter-weight identity attestation that succeeds even when N1MM isn't broadcasting.

无需输入参数。

n1mm_current_state

N1Mm Current State

Complete station snapshot — connection, contest, operator, radios. Returns connection status, contest info, operator callsign, and full radio state for Radio 1 (and Radio 2 if SO2R). This is the first tool any AI session should call.

输入参数station_name

n1mm_lookup

N1Mm Lookup

Pre-log callsign lookup — THE Contest-Copilot trigger. Fires when operator types a callsign and presses spacebar in N1MM. Returns the lookup data plus current band/mode from RadioInfo. Check lookup_age_ms — if >30000, the advice window has closed.

输入参数station_name

n1mm_contacts

N1Mm Contacts

QSO log — recent contacts, edits, and deletes. Returns the last QSO, filtered recent QSOs, recent edits, and recent deletes in one coherent snapshot.

输入参数bandmodecountsincecall_patternstation_name

n1mm_bandmap

N1Mm Bandmap

Live bandmap — spots, mult targets, and activity summary. Returns active spots (with TTL eviction), unworked multipliers, and per-band spot activity counts in one snapshot.

输入参数bandmodecallsignmults_onlystation_name

n1mm_performance

N1Mm Performance

Complete performance snapshot — score, rate, bands, run/S&P, timeline. Returns score, rolling rates (10m/30m/60m), rate derivative for band exhaustion detection, per-band breakdown, per-mode breakdown, hourly summary, and run vs S&P stats in one coherent view.

输入参数bandmodestation_name

n1mm_multipliers

N1Mm Multipliers

Multiplier status — worked mults, mult map, and available needs. Returns total mults worked, per-band mult grid, unworked mults currently spotted, and mult value analysis.

输入参数bandstation_name

n1mm_clock

N1Mm Clock

Contest clock — timing, off-time, and pacing in one view.

输入参数target_qsosstation_nametarget_scoreduration_hoursmin_gap_minutes

n1mm_so2r

N1Mm So2R

Two-radio (SO2R) view: both radios now, and how they've been used. Returns each radio's band, frequency, mode and run/transmit state, N1MM's transmit focus and receive focus, whether both radios are on the same band, each radio's share of N1MM-keyed transmit time (a paddle or PTT isn't reported by N1MM) and minutes per band, transmit- and receive-focus swaps, QSOs per radio, and QSOs made on one radio while the other was running. Timing covers the RadioInfo packets seen since the MCP server started (or the contest changed). Read from N1MM's broadcasts; no rig is read.

输入参数station_name

n1mm_network

N1Mm Network

Every networked N1MM station at once (multi-op). Per station: operator, radios (band, mode, running, transmitting), QSOs, rate over 10 and 60 minutes, mults in the last hour, minutes since the last QSO, the band of its recent QSOs with minutes on it and band changes in the last hour, and when it was last heard. Also: which stations are on each band, stations sharing a band and mode, each station's contest score (shared per contest call), and QSOs per operator this hour against the hour before.

无需输入参数。

n1mm_pileup

N1Mm Pileup

DXpedition pileup view: rate, who's calling, dupes, split, dead air. Over the last window_minutes (default 60, 5 to 1440): QSOs, unique calls, dupes (a call already worked on that band and mode), run share, rate over 5, 15 and 60 minutes and the best 10 minutes in the window, QSOs and share by continent, the top 10 country prefixes, QSOs by band and mode, gaps of 2 minutes or more between QSOs, and the active radio's split (RX, TX, kHz up).

输入参数station_namewindow_minutes

n1mm_diagnostics

N1Mm Diagnostics

Server health and diagnostics — connection, parse errors, memory. Essential for production debugging. First tool to call when something goes wrong during a contest.

输入参数station_name

版本历史

9
  1. v0.4.0最新Oct 26, 2026
  2. v0.3.2Oct 26, 2026
  3. v0.3.1Oct 26, 2026
  4. v0.3.0Oct 19, 2026
  5. v0.2.1Oct 11, 2026
  6. v0.2.0Oct 7, 2026
  7. v0.1.8Oct 6, 2026
  8. v0.1.7Oct 4, 2026
  9. v0.1.6Sep 29, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分