
Cq Zones Mcp
io.github.qso-graphv0.1.0Updated Oct 7, 2026
CQ zones as CQ publishes them (WAZ Zone Definitions), in ADIF's DXCC and subdivision codes
Overview
Serves CQ zone reference data, letting an assistant look up CQ WAZ zones, their DXCC entities and subdivisions, and which zones cover a given entity.
- What it does
- Provides read-only lookups over CQ's WAZ Zone Definitions (2018-04-01): the 40 CQ zones, their names, entities, subdivisions and boundaries in ADIF DXCC and subdivision codes. Tools include cq_zones_lookup for one zone, cq_zones_codes_for for the zones covering a DXCC entity or subdivision, cq_zones_search by name, prefix or wording, cq_zones_valid_on for date validity, plus source and version info. Every answer cites the zone it comes from.
- When to use it
- Useful for amateur radio work involving CQ zones, such as the Worked All Zones award or the CQ World Wide DX Contest, or when mapping DXCC entities and subdivisions to zones. It is a small, self-contained reference server rather than a general-purpose tool.
- Requirements
- Runs locally as a stdio process, typically launched with uvx cq-zones-mcp, so a Python runtime and uv/uvx are needed. No network access, authentication, API keys or environment variables are required; the zone facts ship with the package.
Installation
In SourceWeft
- Open Cq Zones Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
cq-zones-mcp
Source: CQ's WAZ Zone Definitions ("Updated and correct as of April 1, 2018"), © CQ Communications, Inc. and the World Wide Radio Operators Foundation (WWROF). The 40 CQ zones are CQ's: this package serves facts from CQ's list, each citing the zone it comes from, and links to CQ's page rather than copying it. Our GPL-3.0 licence covers our code, not CQ's data.
Checked against: AD1C's country files (Jim Reisert, AD1C), ADIF 3.1.7's subdivision zones, and ARRL's DXCC list. The tests fetch AD1C's and ARRL's files from their sites to validate the facts; neither is included here. where they differ, the owner's list wins (see docs/TRANSCRIPTION.md).
MCP server for CQ zones as CQ publishes them: the 40 zones of CQ's WAZ Zone Definitions (2018-04-01), the zones used by CQ's Worked All Zones award and the CQ World Wide DX Contest. Each zone's entities and subdivisions are given in ADIF's own DXCC and subdivision codes, with CQ's own wording where it splits an area.
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
Tools
Quick Start
No credentials needed — just install and configure your MCP client.
Configure your MCP client
cq-zones-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):
Claude Code
Add to .claude/settings.json:
ChatGPT Desktop
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
Ask questions
"Which CQ zone is Quebec in?"
"What does CQ zone 23 cover?"
"Which CQ zones does Canada span?"
MCP Inspector
Then open the MCP Inspector at http://localhost:8016.
Development
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
cq-zones-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.
Source: README.md at commit f7acfa9
Tools
0Version history
1- v0.1.0LatestOct 7, 2026
