About darc-dok-mcp
darc-dok-mcp is an MCP server for radio operators and applications using DARC DOKs. It provides local-club and special-event codes from DARC’s lists, including validity periods for special DOKs, with source citations and no network access required.
Key features
- 01Look up DOK and special-DOK details
- 02Check a code’s validity on a date
- 03Search by club, town, district, or purpose
- 04View source, editions, and version details
Use cases
- 01Identify the club associated with a DOK
- 02Check whether a special DOK applied on a QSO date
- 03Find DOKs by district or town
MCP support
Exposes tools to MCP clients for looking up, searching, and checking DARC DOK data. The facts are bundled with the package, and answers identify their source.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
6Saved tool list · updated 2d ago
This tool takes no parameters.
Details
From the project READMEdarc-dok-mcp
Source: the Deutscher Amateur-Radio-Club e.V. (DARC): the DOK-Liste (DARC DX-Referat, by Karsten Radwan, DL2ABM, 26.12.2016) and the special-DOK list (DARC SDOK-Referat). DOKs are DARC's: this package serves the lists' rows as facts, each citing its page or row, and links to DARC's files rather than copying them. Our GPL-3.0 licence covers our code, not DARC's data.
MCP server for DARC DOKs and special DOKs as DARC publishes them: the local-club codes of DARC's DOK-Liste (2016-12-26) and the event codes of DARC's special-DOK list, with each special DOK's validity window. DOKs are used for DARC's DLD award, the DOK best-lists and the WAG contest, and in ADIF's DARC_DOK field.
Part of the qso-graph project. No network, no authentication: the facts from the owner's list ship with the package, and every answer names its source.
Install
uvx darc-dok-mcp # run it; nothing to install
Tools
| Tool | Description | Key Parameters |
|---|---|---|
darc_dok_lookup | One DOK or special DOK: district and club, or purpose, callsign, window and sponsoring club | code |
darc_dok_valid_on | Whether a DOK or special DOK was valid on a QSO's date | code, on_date |
darc_dok_search | Find DOKs by club, town, district or purpose | text, limit |
darc_dok_codes_for | Kept for the shared tool set; DOKs map to no ADIF subdivision | dxcc, subdivision |
darc_dok_source_info | Owner, editions, terms, and the owner's files' URLs and SHA-256s | — |
get_version_info | Service version + the owner's edition served (fleet identity attestation) | — |
Quick Start
No credentials needed — just install and configure your MCP client.
Configure your MCP client
darc-dok-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": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
ChatGPT Desktop
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"darc-dok": {
"command": "uvx",
"args": ["darc-dok-mcp"]
}
}
}
Ask questions
"Which club is DOK A01?"
"Was special DOK 01ALT valid on 2004-06-01?"
"Which DOKs are in district Baden?"
MCP Inspector
darc-dok-mcp --transport streamable-http --port 8018
Then open the MCP Inspector at http://localhost:8018.
Development
git clone https://github.com/qso-graph/darc-dok-mcp.git
cd darc-dok-mcp
uv sync --group dev
uv run pytest
scripts/fetch_published.py fetches the owner's document(s) into published/ (not committed) and checks their SHA-256s; uv run pytest --live runs the tests that need them. scripts/build.py regenerates derived/ and load.sql, a PostgreSQL load for QSO Graph's reference data (load QG ADIF's adif schema first).
License
darc-dok-mcp's own code is GPL-3.0-or-later. See LICENSE. The data it serves is the owner's, credited at the top of this page: our licence doesn't cover it, and we claim no rights in it. The owner's document itself is not included; data/SOURCE.json records its URL and SHA-256 so anyone can check the facts against it. Files we built from the facts (data/derived/) are ours and labelled as ours. How the owner's text was read is recorded in docs/TRANSCRIPTION.md. See NOTICE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.