lotw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOTW_MCP_MOCK | No | Set to '1' to enable mock mode for testing without real credentials. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get lotw-mcp service version and upstream LoTW schema version. Returns the running PyPI version of lotw-mcp and the ARRL LoTW ADIF/CSV export schema in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol. Returns: service_name, service_version (PyPI), and spec_version (LoTW schema). |
| lotw_confirmationsC | Query confirmed QSL records from LoTW. |
| lotw_qsosC | Query all uploaded QSOs from LoTW (confirmed and unconfirmed). |
| lotw_dxcc_creditsC | Query DXCC award credits from LoTW confirmations. |
| lotw_downloadA | Download your complete LoTW log as raw ADIF text. Returns the .adi file content — save to disk for import into your logger. Set qsl_only=True for confirmed QSLs only. Omit 'since' for full history. Warning: large logs may take 30-60 seconds (LoTW is slow). |
| lotw_user_activityA | Check if a callsign uses LoTW and when they last uploaded. Public endpoint — no authentication required. Uses a locally cached copy of the LoTW user activity CSV (refreshed weekly). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of LoTW functionality: version info, confirmations, full log download, DXCC credits, all QSOs, and user activity. No two tools have overlapping purposes.
Most tools use 'lotw_' prefix but 'get_version_info' breaks this pattern. Additionally, some tool names are verbs ('lotw_download') while others are nouns ('lotw_confirmations'), introducing inconsistency.
With 6 tools, the server covers the core LoTW data retrieval operations without being too sparse or overwhelming. A slightly larger set might include upload or more granular queries, but the current count is appropriate for this domain.
The tool set provides most essential LoTW operations: version checking, log downloading, QSO querying (confirmed and all), DXCC credits, and user activity. Missing only upload functionality and perhaps station-specific queries, but these are minor gaps.