mcpField
Q
qso-graph-contest-mcp

qso-graph-contest-mcp

Local
github.com/qso-graphGames & Entertainment0Updated today
Repository

About qso-graph-contest-mcp

qso-graph-contest-mcp is a planned MCP server for amateur-radio contest schedules and rules. It is currently in development and exposes only version and development-status information; contest lookup is not available yet.

Key features

  1. 01Report service version
  2. 02Report development status
  3. 03Point to the development tracker

Use cases

  1. 01Check whether contest features are available
  2. 02Find where planned work is tracked

MCP support

Currently exposes only the `get_version_info` tool to MCP clients; contest schedule and rules tools are planned but not implemented.

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-qso-graph-contest": {
      "command": "uvx",
      "args": [
        "qso-graph-contest-mcp"
      ]
    }
  }
}
Run commanduvx qso-graph-contest-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
pypiqso-graph-contest-mcp0.1.0

Tools

1

Saved tool list · updated 2d ago

This tool takes no parameters.

Details

From the project README

qso-graph-contest-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.

Which contests are running now, what is coming, and the rules, exchange and multipliers for each — with every contest citing the sponsor that published its rules. Named for this project rather than any sponsor: a server covering many sponsors' contests cannot take one sponsor's name.

Planned work, including the data sources it would use and whether each is actually available, is tracked in qso-graph-devel#49.

Part of the qso-graph project.

Install

uvx qso-graph-contest-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

qso-graph-contest-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": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}
Claude Code

Add to .claude/settings.json:

{
  "mcpServers": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}
ChatGPT Desktop

Configure via Settings > Apps & Connectors, or in your agent definition:

{
  "mcpServers": {
    "qso-graph-contest": {
      "command": "uvx",
      "args": ["qso-graph-contest-mcp"]
    }
  }
}
Questions it will answer

Not yet — these are what the finished server is for:

"What contests are running this weekend?"

"What is the exchange for this contest, and who sponsors it?"

"Which upcoming contests are CW only on 40m?"

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.