aprs-mcp
MCP server that exposes APRS-IS network tools to LLM agents, enabling sending APRS messages, querying positions, finding nearby stations, and listening to live packet streams.
README
aprs-mcp
Model Context Protocol (MCP) server exposing the APRS-IS network as tools for
any LLM agent (opencode, Claude Desktop, Cursor, Windsurf, generic MCP
clients). Built on aprslib and fastmcp.
[!IMPORTANT] APRS transmissions are public. Only transmit with a valid amateur-radio callsign and in accordance with the rules that apply in your jurisdiction.
Tools
| Tool | Purpose |
|---|---|
aprs_cmd_list() |
List the APRS commands exposed by this MCP server |
aprs_send_message(to_callsign, message) |
Send an APRS message (max ~60 chars) |
aprs_position(callsign, timeout=120) |
Last known position, aprs.fi API first, live stream fallback |
aprs_nearby(lat, lon, radius_km, timeout=8) |
Stations transmitting within a radius |
aprs_listen(filter_text, duration=5, max_packets=50, raw=false) |
Stream raw or parsed packets against an APRS-IS filter |
aprs_listen filter syntax
| Example | Meaning |
|---|---|
s/NOCALL |
Station NOCALL |
r/-33.9/18.4/50 |
Radius filter around lat/lon, 50 km |
m/NOCALL |
Messages to/from NOCALL |
t/po |
Positions and objects only |
Requirements
Requires Python 3.11+ and uv.
Installation
git clone https://github.com/gflerm/aprs-mcp.git
cd aprs-mcp
uv sync
cp credentials.example credentials
On Windows PowerShell, the included installer creates the virtual environment and credentials template:
.\install.ps1
MCP client configuration
Codex
Register the local STDIO server globally:
codex mcp add aprs -- ".venv\Scripts\aprs-mcp.exe"
On macOS or Linux, use .venv/bin/aprs-mcp instead. Restart Codex after
registration, then run aprs_cmd_list to verify the connection.
Other clients
opencode — add to ~/.config/opencode/opencode.json:
{
"mcp": {
"aprs": {
"type": "local",
"command": [".venv/bin/aprs-mcp"],
"enabled": true
}
}
}
Claude Desktop — add to claude_desktop_config.json under mcpServers.
Any other MCP client — point it at the mcp stdio transport with command
.venv/bin/aprs-mcp (Windows: .venv\Scripts\aprs-mcp.exe).
Restart the agent after registering the server.
Credentials
The server reads network settings and station identity from a plain
key=value file named credentials in the project. Copy
credentials.example to credentials and fill in your own values.
The server looks for credentials in this order:
- Next to the installed module (site-packages)
- The project root (the checkout / install directory)
- The current working directory
Existing environment variables always win; the file never overrides them.
Populate the credentials file as follows:
| Key | Type | Meaning |
|---|---|---|
APRS_CALLSIGN |
required | Your base callsign, e.g. ZL1ABC. Never transmit with NOCALL. |
APRS_PASSCODE |
required | APRS-IS passcode for the callsign. Use -1 for receive-only |
APRS_HOST |
optional | APRS-IS server, default euro.aprs2.net |
APRS_PORT |
optional | Default 14580 (140 for legacy tin) |
APRSFI_API_KEY |
optional | aprs.fi API key for fast aprs_position lookups |
APRS_NTP_HOST |
optional | NTP server for local timezone, default xxx.xxx.xxx.xxx |
Getting your passcode. The passcode is a one-way hash of your base
callsign — generate it once with the APRSPASS calculator shipped inside
aprslib:
python -c "from aprslib import passcode; print(passcode('ZL1XXXX'))"
Then write the result into credentials:
APRS_CALLSIGN=ZL1XXXX
APRS_PASSCODE=12345
APRS_HOST=euro.aprs2.net
APRS_PORT=14580
Optionally add your aprs.fi key (free, low-volume) so aprs_position
answers without waiting on the live stream.
credentials is your real file. credentials.example is the committed
template. Never commit credentials.
Development
Install the project in its managed virtual environment:
uv sync
uv run python -m aprs_mcp.server
The MCP transport uses standard input/output. Client logs and diagnostics must go to standard error so they do not corrupt the protocol stream.
License
Released under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
E2B
Using MCP to run code via e2b.