Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
ADIF 3.1.7 spec engine for amateur radio logs: validation, parsing, enumerations, geospatial.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"adif": {
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add adif -- uvx adif-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"adif": {
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"adif": {
"type": "stdio",
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 qso-graph 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(2.1.1)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Spec Driven Development, Remote Desktop Commander, First Sale Scout
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Playbooks and a 14-day checklist for founders winning their first paying customers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for the ADIF 3.1.7 specification: validate and parse ADIF records, search the spec's fields, enumerations and data types, and compute distance and heading between Maidenhead locators, through any MCP-compatible AI assistant.
Part of the qso-graph project. No authentication required — the ADIF specification is bundled, so it works offline.
uvx adif-mcp # run it; nothing to install
| Tool | Description | Key Parameters |
|---|---|---|
validate_adif_record | Validate a raw ADIF record against the 3.1.7 spec | adif_string |
parse_adif | Streaming parser for large ADIF files, with pagination | file_path, start_at, limit |
read_specification_resource | Raw JSON for any spec module (band, mode, fields, ...) | resource_name |
list_enumerations | All ADIF enumerations with entry counts | — |
search_enumerations | Search enumeration records by keyword | search_term, enumeration |
calculate_distance | Great-circle distance (km) between two Maidenhead locators | start, end |
calculate_heading | Initial beam heading (azimuth) between two locators | start, end |
get_version_info | Service version + upstream spec version (fleet identity attestation) | — |
ADIF (Amateur Data Interchange Format) is the standard file format amateur radio logging programs use to exchange QSO records. adif-mcp is the specification package of qso-graph: it validates, parses and searches ADIF so an assistant can work with logs safely and accurately. Credentials are handled separately by qso-graph-auth, and each logging service has its own MCP server (see qso-graph.io).
No credentials needed — just install and configure your MCP client.
adif-mcp works with any MCP-compatible client. Add the server config and restart. The tools appear automatically.
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
Add to .claude/settings.json:
{
"mcpServers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
Configure via Settings > Apps & Connectors, or in your agent definition:
{
"mcpServers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": { "adif": { "command": "uvx", "args": ["adif-mcp"] } } }
"Is this ADIF record valid? KI7MT 20260928 20m SSB "
"What values does the ADIF MODE enumeration allow for digital modes?"
"Parse my log file and show me the first 50 QSOs."
"How far is it from DN13 to JN48, and what heading should I point the beam?"
adif-mcp ships ADIF 3.1.7 as ADIF publishes it: 186 fields, 25 enumerations and 28 data types. validate_adif_record checks each field against its ADIF data type and, for enumerated fields, against the enumeration:
BAND=15M is accepted as 15m.CREDIT_SUBMITTED (a list of Credit or Credit:Medium entries) are checked entry by entry.MODE=MFSK with SUBMODE=FT4.Location (XDDD MM.MMM), Boolean (Y or N), and IOTA, WWFF, POTA and SOTA references. What the grammar allows but cannot be right, such as a latitude over 90 degrees or N/S on a longitude, is a warning, never an error.The server also publishes the MCP resource adif://system/version: the service version and the ADIF specification version it serves.
adif-mcp --transport streamable-http --port 8003
Then open the MCP Inspector at http://localhost:8003.
git clone https://github.com/qso-graph/adif-mcp.git
cd adif-mcp uv sync --group dev uv run pytest
adif-mcp's own code is GPL-3.0-or-later. See LICENSE for details.
The ADIF specification files are not ours. The package includes ADIF's published files for two versions, the previous and the current (3.1.6 and 3.1.7 today), unmodified: every file in ADIF's resource zip except its test material, in every format ADIF publishes (JSON, XML with all.xml and the XSD, CSV, TSV, XLSX, ODS), with a MANIFEST.json of their SHA-256s per version, from the ADIF Developers Group. They are ADIF's work, and our licence doesn't cover them. The only files in that folder that are ours are the derived Country enumeration and each version's MANIFEST.json. See NOTICE.