Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
ADIF 3.1.7 spec engine for amateur radio logs: validation, parsing, enumerations, geospatial.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"adif": {
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}Run this in your terminal
claude mcp add adif -- uvx adif-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"adif": {
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"adif": {
"type": "stdio",
"command": "uvx",
"args": [
"adif-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account qso-graph, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.1.1) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.