Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
QRZ.com MCP server. Callsign lookup, DXCC resolution, logbook queries via QRZ XML API.
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": {
"qrz": {
"command": "uvx",
"args": [
"qrz-mcp"
]
}
}
}Run this in your terminal
claude mcp add qrz -- uvx qrz-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"qrz": {
"command": "uvx",
"args": [
"qrz-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": {
"qrz": {
"type": "stdio",
"command": "uvx",
"args": [
"qrz-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 8, 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 (0.6.3) reached the registry today.
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, aamio rendezvous
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ 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.
Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.
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 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.
uvx qrz-mcp # run it; nothing to install
| 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) |
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
qso-graph-auth persona add --name ki7mt --callsign KI7MT --start 2018-01-01
qso-graph-auth provider enable ki7mt qrz qso-graph-auth creds set ki7mt qrz # asks for your username, then your password (hidden)
qso-graph-auth provider enable ki7mt qrz_logbook qso-graph-auth creds set ki7mt qrz_logbook # asks for your username, then your API key
qso-graph-auth creds doctor
Pass the persona name (ki7mt above) as the persona argument on every tool call.
Omit
--password/--api-keyto 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.
qrz-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": { "qrz": { "command": "uvx", "args": ["qrz-mcp"] } } }
Add to .claude/settings.json:
{
"mcpServers": { "qrz": { "command": "uvx", "args": ["qrz-mcp"] } } }
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"] } } }
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": { "qrz": { "command": "uvx", "args": ["qrz-mcp"] } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "qrz": { "command": "uvx", "args": ["qrz-mcp"] } } }
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": { "qrz": { "command": "uvx", "args": ["qrz-mcp"] } } }
"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"
QRZ enforces undocumented rate limits that can trigger 24-hour IP bans. qrz-mcp protects you:
Set the mock environment variable to test all 6 tools without QRZ credentials:
QRZ_MCP_MOCK=1 qrz-mcp
qrz-mcp --transport streamable-http --port 8002
Then open the MCP Inspector at http://localhost:8002.
git clone https://github.com/qso-graph/qrz-mcp.git
cd qrz-mcp uv sync --group dev uv run pytest
| 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 |
GPL-3.0-or-later