Skip to main content

qrz-mcp

PyPI MCP Registry

MCP server for QRZ.com — callsign lookups, DXCC entity resolution, and logbook queries through any MCP-compatible AI assistant.

Part of the qso-graph project. Uses qso-graph-auth for credential management.

Install

uvx qrz-mcp            # run it; nothing to install

Tools

Tool API Auth Description
qrz_lookup XML Session key Callsign lookup (name, grid, DXCC, license class, QSL info, image)
qrz_dxcc XML Session key DXCC entity resolution from callsign or entity code
qrz_logbook_status Logbook API key Logbook stats (QSO count, DXCC total, date range)
qrz_logbook_fetch Logbook API key Query QSOs with filters and transparent pagination
qrz_download Logbook API key Download full logbook as ADIF
get_version_info — None Service version + upstream QRZ API version (fleet identity attestation)

Quick Start

1. Set up credentials

qrz-mcp uses qso-graph-auth personas for credential management. QRZ has two separate auth mechanisms, exposed as two providers — set up whichever you need:

Provider Tools Credentials
qrz qrz_lookup, qrz_dxcc username + password
qrz_logbook qrz_logbook_status, qrz_logbook_fetch, qrz_download username + API key
# Install qso-graph-auth if you haven't
uv tool install qso-graph-auth

# Create a persona (--start is required)
qso-auth persona add --name ki7mt --callsign KI7MT --start 2018-01-01

# XML API (qrz_lookup, qrz_dxcc)
qso-auth provider enable ki7mt qrz
qso-auth creds set ki7mt qrz              # asks for your username, then your password (hidden)

# Logbook API (qrz_logbook_status, qrz_logbook_fetch, qrz_download)
qso-auth provider enable ki7mt qrz_logbook
qso-auth creds set ki7mt qrz_logbook      # asks for your username, then your API key

# Verify
qso-auth creds doctor

Pass the persona name (ki7mt above) as the persona argument on every tool call.

Omit --password / --api-key to be prompted instead — passing secrets as CLI arguments leaves them in your shell history.

XML API (callsign lookup, DXCC) requires a QRZ XML Subscription ($35.95/yr). Free tier returns name and address only.

Logbook API requires an API key from QRZ Settings > API.

2. Configure your MCP client

qrz-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": {
    "qrz": {
      "command": "uvx",
      "args": ["qrz-mcp"]
    }
  }
}

Claude Code

Add to .claude/settings.json:

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

ChatGPT Desktop

ChatGPT supports MCP via the OpenAI Agents SDK. Add under Settings > Apps & Connectors, or configure in your agent definition:

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

Cursor

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

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

VS Code / GitHub Copilot

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

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

Gemini CLI

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

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

3. Ask questions

"Look up W1AW on QRZ — what's their grid and license class?"

"What DXCC entity is VP8PJ?"

"How many QSOs do I have in my QRZ logbook?"

"Show me all 20m FT8 QSOs from my QRZ logbook this year"

Rate Limiting

QRZ enforces undocumented rate limits that can trigger 24-hour IP bans. qrz-mcp protects you:

  • 500ms minimum delay between all API calls
  • Token bucket: 35 requests/minute
  • 60s freeze on authentication failures
  • 3600s freeze on connection refused (IP ban detection)
  • In-memory response cache (5 min for callsigns, 1 hour for DXCC)

Testing Without Credentials

Set the mock environment variable to test all 6 tools without QRZ credentials:

QRZ_MCP_MOCK=1 qrz-mcp

MCP Inspector

qrz-mcp --transport streamable-http --port 8002

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

Development

git clone https://github.com/qso-graph/qrz-mcp.git
cd qrz-mcp
uv sync --group dev
uv run pytest

QRZ Subscription Tiers

Feature Free XML Data ($35.95/yr)
Callsign lookups/day 100 Unlimited
Fields returned Name + address only All (grid, lat/lon, DXCC, class, QSL, image)
Logbook API No Yes
DXCC lookup No Yes

License

GPL-3.0-or-later

Metadata

Release files for qrz-mcp 0.3.9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for qrz-mcp 0.3.9
File Size Uploaded
qrz_mcp-0.3.9.tar.gz 186.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for qrz-mcp 0.3.9
File Interpreter ABI Platform
qrz_mcp-0.3.9-py3-none-any.whl Python 3 none any Details

Total release size: 218.0 kB

Release files / qrz_mcp-0.3.9.tar.gz

Download URL qrz_mcp-0.3.9.tar.gz
Size 186.7 kB
Tags Source
SHA-256 checksum
How to use checksums
6cdbe1f5a348194c6e9ff917e2f5b88925758085ba0b46982efe02aae0a0b952
BLAKE2b-256 checksum
How to use checksums
8b80d315d034a74f7d74939a3c1c9f1746f527fd3d9535be5cd14353314f7f52
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / qrz_mcp-0.3.9-py3-none-any.whl

Download URL qrz_mcp-0.3.9-py3-none-any.whl
Size 31.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
10e7ec1a2d799944f036f868602446a571b371a9da60725c9988cd078a4ed5c5
BLAKE2b-256 checksum
How to use checksums
a64ceb2bdf443e1f957a08eb50571577d51ddd8ebf8bceaeefd8cdfa7b93be80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.1

2 release files

0.4.0

2 release files

This release

0.3.9 This release

2 release files

0.3.8

2 release files

0.3.7

2 release files

0.3.6

2 release files

0.3.5

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.2

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page