io.github.qso-graph/pota-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POTA_MCP_MOCK | No | Set to 1 to mock the POTA API for testing without network. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_version_infoA | Get pota-mcp service version and upstream spec version. Returns the running PyPI version of pota-mcp and the POTA API revision currently in use. Use this to confirm fleet alignment across MCP deployments — agents can compare service_version and spec_version across servers to detect drift without going outside the MCP protocol. Returns: service_name, service_version (PyPI), and spec_version (POTA API). |
| pota_spotsA | Get current POTA activator spots. Returns live spot feed with park details, grid squares, and coordinates. All filters are optional — omit to get all active spots. |
| pota_park_infoB | Get detailed park information by POTA reference code. |
| pota_park_statsB | Get activation and QSO counts for a POTA park. |
| pota_user_statsA | Get POTA activator and hunter statistics for a callsign. |
| pota_scheduledA | Get upcoming scheduled POTA activations. Returns: List of scheduled activations with activator, park, date, time window, planned frequencies, and comments. |
| pota_location_parksA | List all POTA parks in a state, province, or country. |
| pota_nearby_parksB | Find POTA parks near a geographic point. Fetches all parks in the given location and filters by distance. Useful for finding 2-fer candidates near an activation site. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct POTA operation: version info, park listing by location, nearby parks, park details, park statistics, scheduled activations, live spots, and user stats. No overlap in functionality.
All tools follow a consistent 'pota_' prefix combined with a verb_noun pattern (e.g., pota_location_parks, pota_park_info, pota_user_stats). The only exception is get_version_info, but it still adheres to a clear verb_noun structure without the prefix.
With 8 tools, the server is well-scoped for its purpose. It covers essential POTA operations without unnecessary bloat or gaps.
The tool surface covers all core POTA functionalities: version checking, park discovery (by location, nearby, info, stats), scheduled activations, live spots, and user statistics. No obvious missing operations for a read-only data API.