mcpField
J
js8call-mcp

js8call-mcp

Local
github.com/qso-graphCommunication0Updated today
Repository

About js8call-mcp

js8call-mcp is an in-development MCP server for read-only access to JS8Call. It currently exposes only version and development-status information; radio data features are planned, and it cannot transmit or control PTT.

Key features

  1. 01Version and development-status lookup
  2. 02Read-only scope planned for JS8Call data
  3. 03No transmit or PTT control

Use cases

  1. 01Check the service version and project status

MCP support

It exposes the `get_version_info` tool to MCP clients. Planned access to JS8Call data is not available yet.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "qso-graph-js8call": {
      "command": "uvx",
      "args": [
        "js8call-mcp"
      ]
    }
  }
}
Run commanduvx js8call-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypijs8call-mcp0.1.0

Tools

1

Saved tool list · updated 3d ago

This tool takes no parameters.

Details

From the project README

js8call-mcp

PyPI

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

ToolDescription
get_version_infoService 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.

Comments

Markdown supported

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.