About dxe-mcp
dxe-mcp is a planned MCP server for radio operators seeking DXpedition status, bands, modes, and QSL routes. It is currently in development and only reports version and development information; DXpedition lookup is not available yet.
Key features
- 01Reports service version
- 02Reports development status
- 03Points to the work tracking location
Use cases
- 01Check whether DXpedition features are available yet
- 02Find the project’s development status
- 03Identify where planned work is tracked
MCP support
Currently exposes only the `get_version_info` tool to MCP clients, reporting the service version, development status, and tracking location. It does not yet provide DXpedition information.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
1Saved tool list · updated 2d ago
This tool takes no parameters.
Details
From the project READMEdxe-mcp
In development
This package is published so the name is held while the work is planned in the open. It registers one tool,
get_version_info, and does nothing else yet. If you install it expecting a working server, that is what you will find — which is why it says so here, in the server's own instructions, and in the one tool it has.PyPI does not reserve a name for a pending trusted publisher, so a name is only held once something is actually published. Given that, a package that says what it is beats an empty one that does not.
Which DXpeditions are on the air now, which are announced, their bands, modes and QSL routes, and online log lookup where a published source allows it.
Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#50.
Part of the qso-graph project.
Install
uvx dxe-mcp # run it; nothing to install
Tools
| Tool | Description |
|---|---|
get_version_info | Service version, development status, and where the work is tracked |
Quick Start
No credentials needed — install and configure your MCP client.
Configure your MCP client
dxe-mcp works with any MCP-compatible client. Add the server config and restart.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS,
%APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"dxe": {
"command": "uvx",
"args": ["dxe-mcp"]
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"dxe": {
"command": "uvx",
"args": ["dxe-mcp"]
}
}
}
ChatGPT Desktop
Configure via Settings > Apps & Connectors, or in your agent definition:
{
"mcpServers": {
"dxe": {
"command": "uvx",
"args": ["dxe-mcp"]
}
}
}
Questions it will answer
Not yet — these are what the finished server is for:
"Which DXpeditions are active right now?"
"What is announced for the next three months, and on which bands?"
"How do I QSL for this expedition?"
Licence
GPL-3.0-or-later. See LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.