js8call-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.
Read-only access to JS8Call's API: the decode stream, stations heard, message traffic and the propagation those imply. No write, no PTT, no transmit control — a permanent constraint, not a first-version limit.
Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#48.
Part of the qso-graph project.
Install
uvx js8call-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
js8call-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": {
"js8call": {
"command": "uvx",
"args": ["js8call-mcp"]
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"js8call": {
"command": "uvx",
"args": ["js8call-mcp"]
}
}
}
ChatGPT Desktop
Configure via Settings > Apps & Connectors, or in your agent definition:
{
"mcpServers": {
"js8call": {
"command": "uvx",
"args": ["js8call-mcp"]
}
}
}
Questions it will answer
Not yet — these are what the finished server is for:
"Who has JS8Call heard on 40m in the last hour?"
"What message traffic has come through for my callsign?"
"Which stations are relaying, and how far away are they?"
Licence
GPL-3.0-or-later. See LICENSE.
Metadata
Release files for js8call-mcp 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| js8call_mcp-0.0.1.tar.gz | 170.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| js8call_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 186.8 kB
Release files / js8call_mcp-0.0.1.tar.gz
| Download URL | js8call_mcp-0.0.1.tar.gz |
|---|---|
| Size | 170.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b9f14fc844fb2932833e7b4fd406b87df24ef39d8be5656880d7739c18fc7cf
|
|
BLAKE2b-256 checksum How to use checksums |
8b02c74ee98899ed83911b754a50ec5cb3e788f2846f04d14379e456e8d25e04
|
| 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 logRelease files / js8call_mcp-0.0.1-py3-none-any.whl
| Download URL | js8call_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
505e94055233ae556c8d2d34acabcd79edf48347de7a07ece2f005641e9d699b
|
|
BLAKE2b-256 checksum How to use checksums |
012cdf06373a9be28a39fc20a81b1ebd27fd45128267ccbc2896b12ce8525ca4
|
| 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