ADIF 3.1.6 parser and validator for amateur radio QSO logs. Full spec coverage.
ADIF 3.1.6 parser and validator for amateur radio QSO logs. Full spec coverage.
adif-mcp · v0.9.3
qso-graph
adif-mcp
Core Model Context Protocol (MCP) server for Amateur Radio Logging, built on the ADIF 3.1.6 specification.
Overview
adif-mcp gives AI agents safe, typed access to Amateur Radio logging data. It validates and parses ADIF records, searches the full ADIF 3.1.6 specification (fields, enumerations, data types), and provides geospatial utilities for Maidenhead locators. A plugin system supports service integrations for LoTW, eQSL, and QRZ.
Quick Start
pip install adif-mcp
Configure Your MCP Client
adif-mcp works with any MCP-compatible client. Add the server config and restart -- tools appear automatically.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"adif": {
"command": "adif-mcp"
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"adif": {
"command": "adif-mcp"
}
}
}
ChatGPT Desktop
Configure via Settings > Apps & Connectors, or in your agent definition:
{
"mcpServers": {
"adif": {
"command": "adif-mcp"
}
}
}
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"adif": {
"command": "adif-mcp"
}
}
}
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"adif": {
"command": "adif-mcp"
}
}
}
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"adif": {
"command": "adif-mcp"
}
}
}
Tools
adif-mcp exposes 7 tools via the Model Context Protocol:
| Category | Tool | Description |
|---|---|---|
| Validation | validate_adif_record |
Validate a raw ADIF string against the 3.1.6 spec |
| Validation | parse_adif |
Streaming parser for large ADIF files with pagination |
| Spec | read_specification_resource |
Retrieve raw JSON for any spec module (band, mode, fields) |
| Spec | search_enumerations |
Search administrative subdivision records |
| Geospatial | calculate_distance |
Great Circle distance (km) between two Maidenhead locators |
| Geospatial | calculate_heading |
Initial beam heading (azimuth) between two locators |
| System | get_version_info |
Active service version and ADIF spec version |
Architecture
adif-mcp is the foundation package -- ADIF spec tools, persona management, and credential storage. Service integrations are separate MCP servers that depend on adif-mcp for identity and auth:
| Package | Status | What It Does |
|---|---|---|
adif-mcp |
Published | ADIF 3.1.6 spec tools + persona/credential management |
lotw-mcp |
Planned | LoTW confirmations, award tracking |
eqsl-mcp |
Planned | eQSL inbox, confirmation status |
qrz-mcp |
Planned | Callsign lookup, logbook queries |
Each integration MCP uses adif-mcp for persona lookup and keyring-backed credentials. Operators install only the servers they need. This keeps each server focused, independently versioned, and free of unnecessary dependencies. |
Compliance & Provenance
adif-mcp follows the ADIF Specification (currently 3.1.6) and uses registered Program IDs to identify all exports:
ADIF-MCP-- Core engineADIF-MCP-LOTW-- LoTW pluginADIF-MCP-EQSL-- eQSL pluginADIF-MCP-QRZ-- QRZ plugin
The project uses APP_ fields for provenance when augmenting records:
APP_ADIF-MCP_OP-- operation performed (normalize,validate,merge)APP_ADIF-MCP-LOTW_ACTION-- LoTW plugin operationAPP_ADIF-MCP-EQSL_TIME-- timestamp of eQSL merge
See the Program ID & APP_ Field Policy for full details.
License
GPL-3.0-or-later. See LICENSE for details.