APRS.fi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_aprs_positionC | Get current position data for a specific callsign from APRS.fi |
| get_aprs_historyC | Get position history for a callsign with time range |
| track_multiple_callsignsC | Track multiple callsigns at once |
| validate_aprs_keyB | Test if an APRS.fi API key is valid |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| set-api-key | Set the APRS.fi API key for this session |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_aprs_history retrieves historical position data, get_aprs_position gets current position, track_multiple_callsigns handles multiple callsigns simultaneously, and validate_aprs_key tests API key validity. The descriptions make it unambiguous which tool to use for each task.
All tools follow a consistent snake_case naming pattern with clear verb_noun structure (get_aprs_history, get_aprs_position, track_multiple_callsigns, validate_aprs_key). The naming is predictable and readable throughout the set.
With 4 tools, this server is well-scoped for APRS.fi data access. Each tool serves a distinct and necessary function for the domain, covering key operations without being overly sparse or bloated. The count aligns perfectly with the server's purpose.
The tool set covers essential APRS.fi operations well: retrieving current and historical position data, tracking multiple callsigns, and validating API keys. A minor gap exists in not having tools for more advanced APRS features like messaging or telemetry, but the core functionality for position tracking is complete.