sota-mcp
MCP server for Summits on the Air (SOTA) — live spots, activation alerts, summit info, and nearby summits through any MCP-compatible AI assistant.
Part of the QSO-Graph project. No authentication required — uses the public SOTA API exclusively.
Install
uvx sota-mcp # run it; nothing to install
Tools
| Tool | Description |
|---|---|
sota_spots |
Current and recent spots with time window and association/mode filters |
sota_alerts |
Upcoming scheduled activation alerts |
sota_summit_info |
Summit details by SOTA reference code |
sota_summits_near |
Find summits near coordinates (geospatial search) |
get_version_info |
Service version + upstream spec version (fleet identity attestation) |
Quick Start
No credentials needed — just install and configure your MCP client.
Configure your MCP client
sota-mcp works with any MCP-compatible client. Add the server config and restart — tools appear automatically.
Claude Desktop
Add to claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows):
{
"mcpServers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
Claude Code
Add to .claude/settings.json:
{
"mcpServers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
ChatGPT Desktop
{
"mcpServers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
Cursor
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
VS Code / GitHub Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
Gemini CLI
Add to ~/.gemini/settings.json (global) or .gemini/settings.json (project):
{
"mcpServers": {
"sota": {
"command": "uvx",
"args": ["sota-mcp"]
}
}
}
Ask questions
"What SOTA spots are active right now?"
"Tell me about summit W7I/SI-001"
"What summits are near Boise, Idaho?"
"Any SOTA alerts for this weekend?"
Testing Without Network
For testing all tools without hitting the SOTA APIs:
SOTA_MCP_MOCK=1 sota-mcp
MCP Inspector
sota-mcp --transport streamable-http --port 8007
Then open the MCP Inspector at http://localhost:8007.
Development
git clone https://github.com/qso-graph/sota-mcp.git
cd sota-mcp
uv sync --group dev
uv run pytest
License
GPL-3.0-or-later
Metadata
Release files for sota-mcp 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sota_mcp-0.1.8.tar.gz | 132.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sota_mcp-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 142.0 kB
Release files / sota_mcp-0.1.8.tar.gz
| Download URL | sota_mcp-0.1.8.tar.gz |
|---|---|
| Size | 132.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7481d47fe881e2230ed2294189efaa15b10a08725fddb164a551d832009a9575
|
|
BLAKE2b-256 checksum How to use checksums |
5b81dd169718263739054ef0ca4fb5fad657ff97ed549d3460898aec8d792d14
|
| 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 6, 2026.
Transparency logRelease files / sota_mcp-0.1.8-py3-none-any.whl
| Download URL | sota_mcp-0.1.8-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c26ddd649d81b5b171fffc266b1d03710a366af9fcac1b1844823833cec417c
|
|
BLAKE2b-256 checksum How to use checksums |
b3b977acd6508caa6279958d00edce0e5dcfc74e7f249a367d65fd79a99ff205
|
| 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 6, 2026.
Transparency log