Cq Zones

cq-zones-mcp

PyPI MCP Registry

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

uvx cq-zones-mcp            # run it; nothing to install

Tools

Tool	Description	Key Parameters
cq_zones_lookup	One zone: its name and every entity, subdivision and boundary CQ lists, with the citation	code
cq_zones_codes_for	Which zones cover an ADIF DXCC entity, or one of its subdivisions	dxcc, subdivision
cq_zones_search	Find zones by name, prefix or wording	text, limit
cq_zones_valid_on	Whether a zone was valid on a date (CQ zones have no validity window)	code, on_date
cq_zones_source_info	Owner, edition, terms, and the owner's file's URL and SHA-256	—
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

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):

{
  "mcpServers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

{
  "mcpServers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

ChatGPT Desktop

{
  "mcpServers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

VS Code / GitHub Copilot

Add to .vscode/mcp.json in your workspace:

{
  "servers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

Gemini CLI

Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):

{
  "mcpServers": {
    "cq-zones": {
      "command": "uvx",
      "args": ["cq-zones-mcp"]
    }
  }
}

Ask questions

"Which CQ zone is Quebec in?"

"What does CQ zone 23 cover?"

"Which CQ zones does Canada span?"

MCP Inspector

cq-zones-mcp --transport streamable-http --port 8016

Then open the MCP Inspector at http://localhost:8016.

Development

git clone https://github.com/qso-graph/cq-zones-mcp.git
cd cq-zones-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

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.