Pota MCP logo

Pota MCP

Queries public Parks on the Air data for live spots, park details, statistics, schedules, and location-based park searches.

Install Pota MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pota-mcp": {
      "command": "uvx",
      "args": [
        "pota-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The pota-mcp MCP server connects AI assistants to public Parks on the Air data for live spots, park records, statistics, and schedules. It runs through `uvx` with no credentials and exposes tools for park, callsign, location, and activation queries. Use it to monitor current activations, research parks, review operator activity, or plan nearby and 2-fer outings. A mock mode is available for testing without contacting the POTA API.

Use cases

  • Monitor current POTA activator spots
  • Look up park details and statistics
  • Check activator or hunter performance
  • Find parks near a location
  • Review upcoming scheduled activations

Key features

  • Live activator spots with park and grid enrichment
  • Park metadata and activation statistics
  • Activator and hunter callsign statistics
  • Scheduled activation lookup
  • Regional and nearby park searches
  • Mock mode for offline testing

Tools11

What Pota MCP lets your agent do. Expand a tool for its parameters.

Self-reported~227 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · pota-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
Tools exposed11Callable tools this server registers over MCP.

How Pota MCP works

What pota-mcp MCP server does

The pota-mcp MCP server gives MCP-compatible AI clients access to Parks on the Air (POTA) information. It covers current activator activity, park metadata, activation and QSO totals, operator statistics, scheduled activations, and geographic park searches. POTA endpoints are public, so normal operation does not require an API key or other credentials.

The service is suited to amateur radio workflows where an assistant needs to answer questions about active parks, operators, or planned activations. For example, it can help identify current CW activity on a band, inspect a park by reference code, list parks in a region, or find parks near a coordinate for a 2-fer plan.

Tools and capabilities

Available MCP tools include:

  • pota_spots: Retrieves current activator spots, with park and grid enrichment plus optional filters.
  • pota_park_info: Looks up a park by reference code and returns details such as its name, grid, type, agencies, and website.
  • pota_park_stats: Reports activation and QSO counts for a park.
  • pota_user_stats: Looks up activator or hunter statistics by callsign.
  • pota_scheduled: Lists upcoming scheduled activations.
  • pota_location_parks: Lists parks within a state, province, or country.
  • pota_nearby_parks: Finds parks near a supplied point.
  • get_version_info: Returns the service version and upstream specification version.

These tools support both live operational questions and reference lookups. The spot tool is the main choice for current activity, while the scheduled and location tools are useful for preparation and trip planning.

How it works

The pota-mcp MCP server runs as a local MCP process and communicates with the configured client through the command shown in the setup example. After the client starts it, the tools become available for natural-language requests. The server queries public POTA data rather than requiring a separate account or credential configuration.

For local testing, setting POTA_MCP_MOCK=1 makes the process use mock data instead of contacting the POTA API. The repository also documents a streamable HTTP mode using port 8006, which can be inspected through the MCP Inspector at http://localhost:8006.

Setup and configuration

Install and run it with uvx pota-mcp; the documented approach does not require a separate package installation. Add an MCP server entry whose command is uvx and whose argument is pota-mcp, then restart the client. The README provides configurations for Claude Desktop, Claude Code, ChatGPT Desktop, Cursor, VS Code with GitHub Copilot, and Gemini CLI.

For development, clone the repository, run uv sync --group dev, and execute the test suite with uv run pytest. No required environment variables are documented. The optional POTA_MCP_MOCK setting is intended for offline testing, not normal production use.

The project is licensed under GPL-3.0-or-later.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pota MCP

pota-mcp is an MCP server that connects AI assistants to public Parks on the Air data. Its main tools retrieve live activator spots, park details, park statistics, callsign statistics, scheduled activations, regional parks, nearby parks, and service version information without requiring authentication.

Run `uvx pota-mcp` and add that command to your MCP client configuration. The documented setup uses `uvx` with `pota-mcp` as its argument, so no separate package installation or credentials are required.

Yes, pota-mcp works with Cursor. Add a server entry using command `uvx` and argument `pota-mcp` to `.cursor/mcp.json` at the project or global level, then restart or reload Cursor so the tools become available.

Set `POTA_MCP_MOCK=1` before starting the server.

Start it with `pota-mcp --transport streamable-http --port 8006`, then open the MCP Inspector at `http://localhost:8006`. This uses the documented streamable HTTP mode rather than the default local command configuration.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPota MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pota-mcp?style=directory)](https://allmcps.com/mcp/pota-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/pota-mcp"><img src="https://allmcps.com/api/badge/pota-mcp?style=directory" alt="Pota MCP on AllMCPs" /></a>